mpv Information
Other Information
- Windows version: Windows 11 25H2
- GPU model, driver and version: RTX 2080
- Source of mpv:
- Latest known working version: NIL
- Issue started after the following happened:
Reproduction Steps
Play a HEVC YUV 444 video (10 bit for example). Notice that it is software decoded.
Expected Behavior
Hardware decoding works.
Actual Behavior
Hardware decoding doesn't work.
As @kasper93 explained in #18172 (comment) :
444 HEVC is supported in official documentation now https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/dxva/ns-dxva-dxva_picparams_hevc_rangeext
I could implement this official extension, but I don't have hardware to test this on, so I won't.
I am willing to try and implement the fix, allowing MPV to utilise D3D11VA's HEVC YUV444 hardware decoder. I would like to get the HEVC 444 8b, 10b and 12b variants all working.
I would greatly appreciate if any MPV developer can provide some guidance, including which files I should look at/edit.
If any developer wants to help and implement the fix but lacks the hardware to test it on, I am more than happy to help run the tests. I have an RTX 2080.
Log File
output_sanitized.txt
Sample Files
No response
I carefully read all instruction and confirm that I did the following:
mpv Information
Other Information
Reproduction Steps
Play a HEVC YUV 444 video (10 bit for example). Notice that it is software decoded.
Expected Behavior
Hardware decoding works.
Actual Behavior
Hardware decoding doesn't work.
As @kasper93 explained in #18172 (comment) :
I am willing to try and implement the fix, allowing MPV to utilise D3D11VA's HEVC YUV444 hardware decoder. I would like to get the HEVC 444 8b, 10b and 12b variants all working.
I would greatly appreciate if any MPV developer can provide some guidance, including which files I should look at/edit.
If any developer wants to help and implement the fix but lacks the hardware to test it on, I am more than happy to help run the tests. I have an RTX 2080.
Log File
output_sanitized.txt
Sample Files
No response
I carefully read all instruction and confirm that I did the following:
--log-file=output.txt.