-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Totally support 10 bit output? #8554
Comments
In windows, yes. And the suggestion would be, stick to d3d11 if you use windows. Probably see #5237 OpenGL and Vulkan do support 10 bit in principle, but not in mpv+windows. I'm not sure about OpenGL, but for vulkan, I think I heard from haasn that it depends on the implementation provided by your video card vendor. If their implementation does not support 10 bit, there is no way for mpv to utilize 10 bit through vulkan API. You can check by running |
vulkaninfo.txt |
i don't think it is weird, since it's not implemented for vulkan i believe. at least auto picking it https://github.com/mpv-player/mpv/blob/master/video/out/vulkan/context.c#L223-L226 for comparison: |
It seems windows users who care about the correct output have no other choices except D3d11. |
You can use |
I know it is useful. |
My monitor:
Queried output: \\.\DISPLAY4, 3840x2160 @ 10 bits
When I test the different
--gpu-api
, I found the differences in the log.--dither-depth=auto
will select 8 bit for Vulkan&Opengl, while 10 bit for D3d11.R10G10B10A2
will be chosen when use Opengl&D3d11, no such message for Vulkan.Reported display depth: 8
; D3d11:Reported display depth: 10
; no such message for Vulkan.So does it mean only the d3d11 support 10 bit output correctly?
Log file
d3d11.log
opengl.log
vulkan.log
The text was updated successfully, but these errors were encountered: