-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Wrong color playing 8bit hevc hardware accelerated #15439
Comments
This is probably a Mesa bug. Can you reproduce this with ffmpeg only?
Replace |
it says: Edit: it's |
That should be hevc_vaapi, sorry. That's not needed anymore though. I just saw that your file is HEVC yuv422p, which can't be hardware decoded on any current hardware afaik, except the upcoming Intel Battlemage gpus. So you're in luck. The bug here is that vaapi shouldn't advertise support for this format, but does. Report here https://github.com/intel/media-driver |
Well apparently it's supposed to work https://www.intel.com/content/www/us/en/docs/onevpl/developer-reference-media-intel-hardware/1-1/overview.html#DECODE-OVERVIEW-11-12 It's probably still a media-driver bug though |
The issue is not the decoding. The issue is that mpv cannot natively display yuyv and must convert to yuv422p. But the intel media driver inaccurately claims it can convert yuyv to yuv422p in hardware and so we try to use this path. But then you get these visual results. When I reported it, they said the driver or hardware isn't actually capable of doing this conversion and they should stop reporting that they can. Personally, I'm not convinced that it's a hardware bug vs a driver bug but what do I know. We can't detect it because there are no errors - just visual problems. |
If you force conversion to xyuv or similar, it will look fine still taking a full hardware path. |
mpv Information
Other Information
Reproduction Steps
The issue is apparent in below pictures.
Expected Behavior
Actual Behavior
Log File
output.txt
Sample Files
output.zip
Additional information
vainfo
I carefully read all instruction and confirm that I did the following:
--log-file=output.txt
.The text was updated successfully, but these errors were encountered: