-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically create an mpv.conf file so that the system does not use the user's own mpv.conf file #670
Comments
No, I would prefer the config be handled by Lively itself: lively/src/livelywpf/livelywpf/Core/Wallpapers/VideoMpvPlayer.cs Lines 103 to 148 in cab6e86
or C:\Users\<UserName>\AppData\Local\Lively Wallpaper\mpv\mpv.conf file if present.
Creating auto-file may conflict with some of the Lively settings in the future due to human error etc.. https://mpv.io/manual/stable/#legacy-auto-profiles
I think this approach would be better. |
Passing --no-config might also work I presume, or specifying the folder where to look for the config. Good idea and thank you for the quick response! |
When using mpv already, most users will have an mpv.conf (likely in %appdata%/mpv/), that gets read first.
If that mpv.conf has somewhat niche options, the Lively mpv option will show a blue screen instead of the video file. I believe the culprit option to be running Vulkan as the video renderer.
Putting a default, minimal config into the folder mentioned here solves this issue neatly without interfering with the user's regular mpv install.
As such, I believe an mpv.conf with minimal options (I use profile=gpu-hq and hwdec=auto only) should be created automatically on install (if there is not yet one at that location already) to avoid running into this issue at all.
The text was updated successfully, but these errors were encountered: