Question: How to get hardware decode of VP9 YUV444 10b working on Intel GPU?

[AndrewKeYanzhe]

mpv Information

mpv v0.41.0-dev-g21351a058 Copyright © 2000-2026 mpv/MPlayer/mplayer2 projects
 built on May 12 2026 19:56:53
libplacebo version: v7.364.0
FFmpeg version: e4396b3
FFmpeg library versions:
   libavcodec      62.11.102
   libavdevice     62.1.102
   libavfilter     11.4.102
   libavformat     62.3.102
   libavutil       60.8.102
   libswresample   6.1.102
   libswscale      9.1.102

Other Information

- Windows version: Windows 11 Microsoft Windows [Version 10.0.26100.8457]
- GPU model, driver and version: Intel Graphics (Meteor Lake Ultra 7 165U)
- Source of mpv: https://nightly.link/mpv-player/mpv/workflows/build/master
- Latest known working version: NIL
- Issue started after the following happened: NIL

Reproduction Steps

Play a VP9 YUV444 10b video.

Expected Behavior

Task Manager shows video decode usage (on my system this works, for H264 NV12)

Actual Behavior

For VP9 YUV444 10b, Task Manager shows 0% video decode usage. CPU usage is high.

The Intel decode matrix https://edc.intel.com/content/www/tw/zh/design/products/platforms/details/meteor-lake-u-p/core-ultra-processor-datasheet-volume-1-of-2/003/hardware-accelerated-video-decode/ says that my Meteor Lake CPU (Ultra 7 165U) supports VP9 decode for 10b 444 YUV up to 8K.

I also tried these configs and HWDEC doesn't work for any of them.

hwdec=d3d11va
gpu-api=d3d11

hwdec=vulkan
gpu-api=vulkan

hwdec=qsv

hwdec=qsv-copy

Log File

output.txt

Sample Files

No response

I carefully read all instruction and confirm that I did the following:

• I tested and confirmed that the issue exists with the latest release version or newer.
• I provided all required information including system and mpv version.
• I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
• I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
• I attached the full, untruncated log file.
• I attached the backtrace in the case of a crash.

[CounterPillow]

What makes you think the hardware supports this?

[AndrewKeYanzhe]

The Intel decode matrix https://edc.intel.com/content/www/tw/zh/design/products/platforms/details/meteor-lake-u-p/core-ultra-processor-datasheet-volume-1-of-2/003/hardware-accelerated-video-decode/ says that my Meteor Lake CPU (Ultra 7 165U) supports VP9 decode for 10b 444 YUV up to 8K.

The video I tested is 2880x1860.

I also used FFMPEG to encode with HWENC QSV for the same file, VP9 10b 444 YUV and it was working.

[CounterPillow]

I see, sorry I didn't read the full opening post.

qsv doesn't work as an option in your case because the ffmpeg that mpv is built against doesn't have it enabled. I wouldn't be surprised if d3d11va etc. simply don't have any considerations for this particular format.

[AndrewKeYanzhe]

Thanks for the info. Do you know if there exists a compiled MPV with QSV?

[AndrewKeYanzhe]

Hmm I tried shinchiro's builds (https://github.com/shinchiro/mpv-winbuild-cmake/releases) mpv-x86_64-v3-20260610-git-304426c.7z.

VP9 YUV444 10b hardware decoding works with hwdec=qsv-copy but not hwdec=qsv. With qsv-copy, Task Manager shows some video decode usage.

However, with qsv-copy, I am getting some video artefacts like a green rectangle covering the bottom 10% of the video for some frames, and also some screen tearing artefacts.

mpv_log.txt

[kasper93]

VP9 YUV444 10b hardware decoding works with hwdec=qsv-copy but not hwdec=qsv. With qsv-copy, Task Manager shows some video decode usage.

Could you check https://bluesky-soft.com/en/DXVAChecker.html if the support for VP9 444 is advertised on dxva interface? Or they only expose it on QSV?

[Andarwinux]

https://github.com/intel/media-driver#decodingencoding-features

tigerlake

Intel(R) UHD Graphics
MPEG2_VLD: D3D11
MPEG2_IDCT: D3D11
VC1_VLD2010: D3D11
VC1_VLD_2_Intel: D3D11
VC1_VLD_Intel: D3D11
WMV9_IDCT: D3D11
VC1_IDCT: D3D11
H264_VLD_NoFGT: D3D11
H264_VLD_Stereo_Progressive_NoFGT: D3D11
H264_VLD_Stereo_NoFGT: D3D11
H264_VLD_Multiview_NoFGT: D3D11
C528916C-C0AF-4645-8CB2-372B6D4ADC2A: D3D11
91CD2D6E-897B-4FA1-B0D7-51DC88010E0A: D3D11
97688186-56A8-4094-B543-FC9DAAA49F4B: D3D11
1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B: D3D11
C346E8A3-CBED-4D27-87CC-A70EB4DC8C27: D3D11
FFC79924-5EAF-4666-A736-06190F281443: D3D11
464BDB3C-91C4-4E9B-896F-225496AC4ED6: D3D11
9B31316B-F204-455D-8A8C-9345DCA77C01: D3D11
AFE4285C-AB63-4B2D-8278-E6BAACEA2CE9: D3D11
277DE9C5-ED83-48DD-AB8F-AC2D24B22943: D3D11
04C5BA10-4E9A-4B8E-8DBF-4F4B48AFA27C: D3D11
0ACEF8BC-285F-415D-AB22-7BF2527A3D2E: D3D11
24D19FCA-C5A2-4B8E-9F93-F8F6EF15C890: D3D11
353ACA91-D945-4C13-AE7E-469060FAC8D8: D3D11
28566328-F041-4466-8B14-8F5831E78F8B: D3D11
6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600: D3D11
B8B28E0C-ECAB-4217-8C82-EAAA9755AAF0: D3D11
8732ECFD-9747-4897-B42A-E534F9FF2B7A: D3D11
E139B5CA-47B2-40E1-AF1C-AD71A67A1836: D3D11
056A6E36-F3A8-4D00-9663-7E9430358BF9: D3D11
5415A68C-231E-46F4-878B-5E9A22E967E9: D3D11
161BE912-44C2-49C0-B61E-D946852B32A1: D3D11
D6D6BC4F-D51A-4712-97E8-750917C860FD: D3D11
7FEF652D-3233-44DF-ACF7-ECFB584DAB35: D3D11
87B2AE39-C9A5-4C53-86B8-A52D7EDBA488: D3D11
10E19AC8-BF39-4443-BEC3-1B0CBFE4C7AA: D3D11
2DEC00C7-21EE-4BF8-8F0E-773F11F126A2: D3D11
C35153A0-23C0-4A81-B3BB-6A1326F2B76B: D3D11
A33FD0EC-A9D3-4C21-9276-C241CC90F6C7: D3D11
310E59D2-7EA4-47BB-B319-500E78855336: D3D11
HEVC_VLD_Main_Intel: D3D11
HEVC_VLD_Main: D3D11
HEVC_VLD_Main10_Intel: D3D11
HEVC_VLD_Main10: D3D11
HEVC_VLD_Main10_Ext: D3D11
HEVC_VLD_Main10_422: D3D11
HEVC_VLD_Main_444: D3D11
HEVC_VLD_Main10_444: D3D11
HEVC_VLD_Main12: D3D11
HEVC_VLD_Main12_422: D3D11
HEVC_VLD_Main12_444: D3D11
HEVC_VLD_Main10_422_Intel: D3D11
HEVC_VLD_Main_444_Intel: D3D11
HEVC_VLD_Main10_444_Intel: D3D11
E4E3CF5B-97D2-4658-AACB-366E3EE2CEEE: D3D11
FD9D9559-0FD3-4917-A9A7-07E714EE9EF9: D3D11
0E4BC693-5D2C-4936-B125-AEFE32B16D8A: D3D11
2F08B5B1-DBC2-4D48-883A-4E7B8174CFF6: D3D11
5467807A-295D-445D-BD2E-CBA8C2457C3D: D3D11
AE0D4E15-2360-40A8-BF82-028E6A0DD827: D3D11
HEVC_VLD_Main12_Intel: D3D11
HEVC_VLD_Main12_422_Intel: D3D11
HEVC_VLD_Main12_444_Intel: D3D11
07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA: D3D11
VP9_VLD_Profile0: D3D11
VP9_VLD_10bit_Profile2: D3D11
VP9_VLD_Intel: D3D11
68A21C7B-D58F-4E74-9993-E4B8172B19A0: D3D11
80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8: D3D11
1D5C4D76-B55A-4430-904C-3383A7AE3B16: D3D11
A7F759DD-5F54-4D7F-8291-42E883C546FE: D3D11
F34FA92F-DC79-474C-B0DB-B7BD4522DF77: D3D11
AV1_VLD_Profile0: D3D11
CA44AFC5-E1D0-42E6-9154-B127186D4D40: D3D11
F9A16190-3FB4-4DC5-9846-C8751F83D6D7: D3D11
50925B7B-E931-4978-A12A-586630F095F9: D3D11
B69C20E0-2508-8790-0305-875499E0A2D0: D3D11
49761BEC-4B63-4349-A5FF-87FFDF088466: D3D11

[kasper93]

but not hwdec=qsv.

We don't support QSV directly. Does it work in other videos? Meaning, does it go through d3d11 frames, which we support or not?

However, with qsv-copy, I am getting some video artefacts like a green rectangle covering the bottom 10% of the video for some frames, and also some screen tearing artefacts.

This is the decoder issue, either in ffmpeg or hardware.

[AndrewKeYanzhe]

VP9 YUV444 10b hardware decoding works with hwdec=qsv-copy but not hwdec=qsv. With qsv-copy, Task Manager shows some video decode usage.

Could you check https://bluesky-soft.com/en/DXVAChecker.html if the support for VP9 444 is advertised on dxva interface? Or they only expose it on QSV?

DXVAChecker says:

Format / Profile	Decoder Interface	Supported Resolution
MPEG2_VLD	DXVA2/D3D11	SD / HD / FHD
MPEG2_IDCT	DXVA2/D3D11	SD / HD / FHD
MPEG2_A	DXVA1	SD / HD / FHD
MPEG2_C	DXVA1	SD / HD / FHD
H264_VLD_NoFGT	DXVA2/D3D11	SD / HD / FHD / 4K
H264_VLD_Stereo_Progressive_NoFGT	DXVA2/D3D11	SD / HD / FHD / 4K
H264_VLD_Stereo_NoFGT	DXVA2/D3D11	SD / HD / FHD / 4K
H264_VLD_Multiview_NoFGT	DXVA2/D3D11	SD / HD / FHD / 4K
VP9_VLD_Profile0	DXVA2/D3D11	SD / HD / FHD / 4K / 8K
VP9_VLD_10bit_Profile2	DXVA2/D3D11	SD / HD / FHD / 4K / 8K
VP9_VLD_Intel	DXVA2/D3D11	SD / HD / FHD / 4K / 8K
AV1_VLD_Profile0	D3D11	SD / HD / FHD / 4K / 8K

[AndrewKeYanzhe]

but not hwdec=qsv.

We don't support QSV directly. Does it work in other videos? Meaning, does it go through d3d11 frames, which we support or not?

However, with qsv-copy, I am getting some video artefacts like a green rectangle covering the bottom 10% of the video for some frames, and also some screen tearing artefacts.

This is the decoder issue, either in ffmpeg or hardware.

I also tested with an H264 8 bit video.

This is the QSV behaviour

• VP9 YUV444 10b
  • Green artifacts/screen tearing
  • MPV shows vp9_qsv, qsv-copy
  • MPV video format shows xv30
• H264 8 bit
  • No artifacts
  • MPV shows h264_qsv, qsv-copy
  • MPV video format shows nv12

My MPV config only has hwdec=qsv-copy

MPV seems to have chosen gpu-next
Display format is rgb10a2 for both cases.

[AndrewKeYanzhe]

This is the ffmpeg command to generate the VP9 YUV444 10b video. I tested with QSV HWENC, but software encoding will probably work too.

ffmpeg -y -f rawvideo -pix_fmt rgb24 -s <width>x<height> -r <fps> -color_range pc -i - -c:v vp9_qsv -pix_fmt xv30le -b:v 250M -maxrate 1000M -bufsize 1000M -low_power 1 -colorspace bt709 -color_primaries bt709 -color_trc bt709 -g 1 -strict_gop 1 <output_video_path>.mp4

[AndrewKeYanzhe]

Some useful links I found detailing DXVA YUV444 10b support (the links mostly mention H265 tho)

H265 support
https://github.com/orgs/LizardByte/discussions/220#discussioncomment-8898271

Nevcairiel/LAVFilters#547

From the LizardByte discussion:

Intel has added custom 4:4:4 DXVA vendor extensions.

First, the hardware decoding side is a complete mess. The standard Microsoft DXVA/D3D11VA API for video decoding does not define decoding profiles for HEVC Main 4:4:4, so some vendors (Intel) have made up their own (which is actually the best case) and others (Nvidia) require use of their own vendor-specific APIs to decode 4:4:4 content. AMD seems to lack 4:4:4 decoding support entirely. FFmpeg, which we use for encoding and decoding, doesn't support these custom 4:4:4 DXVA vendor extensions either, so we'd also need to write a FFmpeg patches to enable them.

[kasper93]

Some useful links I found detailing DXVA YUV444 10b support (the links mostly mention H265 tho)

H265 support https://github.com/orgs/LizardByte/discussions/220#discussioncomment-8898271

Nevcairiel/LAVFilters#547

From the LizardByte discussion:

Intel has added custom 4:4:4 DXVA vendor extensions.

First, the hardware decoding side is a complete mess. The standard Microsoft DXVA/D3D11VA API for video decoding does not define decoding profiles for HEVC Main 4:4:4, so some vendors (Intel) have made up their own (which is actually the best case) and others (Nvidia) require use of their own vendor-specific APIs to decode 4:4:4 content. AMD seems to lack 4:4:4 decoding support entirely. FFmpeg, which we use for encoding and decoding, doesn't support these custom 4:4:4 DXVA vendor extensions either, so we'd also need to write a FFmpeg patches to enable them.

Why are we changing topic now? HEVC support is completely different story to your question about VP9 support. Support for HEVC is d3d11va is possible, VP9 is not. I didn't mention the former, because whole there is about VP9.