Closed notmentaloutlaw closed 1 year ago
It's appears to be a vaapi bug that never got squashed.
There is nothing on my end that I can do about it.
Look for details.
Here are some examples I have:
Thanks for the info I will create an issue on mpv side to say that this issue persists when the --vo=libmpv as this issue does not exist when the --vo=gpu for example. Hopefully that will fix things. Although this isn't confirmed I think if you dont use hardware acceleration you wont get this issue. Although depending on your cpu it will just eat it up, which is annoying.
this issue does not exist when the --vo=gpu for example
Odd. I found this issue using mpv normally, although it's a bit rarer. I'm more likely to spot this issue with mpvpaper, as it's running all day long.
Also --vo=libmpv
is not the issue here, it's pretty much --vo=gpu
but in library form.
Look at the mpv docs here: https://mpv.io/manual/master/#video-output-drivers-libmpv
"This also supports many of the options the gpu VO has, depending on the backend." (which is OpenGL here)
hwdec=vaapi
is where you should set your eyes on as hwdec=no
"fixes" the issue (at least on my end).
yeah you are right it is the hardware acceleration that is the issue as if I just use the cpu it just works as intended. However, what baffles me is if I watch a 2 hour movie using mpv and hwdec=vaapi everything is fine there is rarely any graphical glitches. but running mpvpaper there is bound to be one within 5 mins.
but running mpvpaper there is bound to be one within 5 mins
I have a similar feeling about that as well. Then again you aren't looping the same video for hours are you? Although, I've definitely had the same exact issue running some videos normally.
Regularly any video that playing experiences random graphical glitches some a lot worse than others. Here is an example of an average glitch. This happens randomly and has no specific cause as far as my experience with it could tell.
What it looks like:
What it should look like:
![normal](https://user-images.githubusercontent.com/115147718/218328914-7c2dd886-9275-4dfb-a07b-eedc583b9c70.png)
My mpvpaper args consist of only --no-audio and --loop. I have an extensive mpv.conf that uses vo=gpu hwdec=vaapi and high quality settings and never experience this issue with mpv. I am on gentoo musl and this issue is the same regardless of window manager I use. I am using the latest version of mpvpaper from git. However mpv is on version 0.35.0
When I run mpvpaper this is the output it gives: