Vaapi hardware decoding 444 HEVC failure

[kebs00n]

Hello. I'm trying to hardware decode 444 HEVC video frame using VAAPI, but it always fallback in software decoding with this error

% ./ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -y -i ../chromium-video-format-tests/media/test/data/blackwhite_yuv444p-frame.hevc 444.yuv -report 
ffmpeg started on 2023-11-14 at 14:33:10
Report written to "ffmpeg-20231114-143310.log"
Log level: 48
ffmpeg version n6.0.1 Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 10 (Debian 10.2.1-6)
  configuration: --prefix=/home/mou/Documents/Dev/FFmpeg/build
  libavutil      58.  2.100 / 58.  2.100
  libavcodec     60.  3.100 / 60.  3.100
  libavformat    60.  3.100 / 60.  3.100
  libavdevice    60.  1.100 / 60.  1.100
  libavfilter     9.  3.100 /  9.  3.100
  libswscale      7.  1.100 /  7.  1.100
  libswresample   4. 10.100 /  4. 10.100
Input #0, hevc, from '../chromium-video-format-tests/media/test/data/blackwhite_yuv444p-frame.hevc':
  Duration: N/A, bitrate: N/A
  Stream #0:0: Video: hevc (Rext), yuv444p(tv), 240x240 [SAR 1:1 DAR 1:1], 25 tbr, 1200k tbn
Stream mapping:
  Stream #0:0 -> #0:0 (hevc (native) -> rawvideo (native))
Press [q] to stop, [?] for help
[hevc @ 0x56076e89c680] Hardware does not offer any usable surface formats.
[hevc @ 0x56076e89c680] Failed setup for format vaapi: hwaccel initialisation returned error.
Output #0, rawvideo, to '444.yuv':
  Metadata:
    encoder         : Lavf60.3.100
  Stream #0:0: Video: rawvideo (444P / 0x50343434), yuv444p(tv, progressive), 240x240 [SAR 1:1 DAR 1:1], q=2-31, 34560 kb/s, 25 fps, 25 tbn
    Metadata:
      encoder         : Lavc60.3.100 rawvideo
frame=    1 fps=0.0 q=-0.0 Lsize=     169kB time=00:00:00.04 bitrate=34560.0kbits/s speed=13.2x    
video:169kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000%

See attached logs

How to reproduce:

% ./ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -y -i blackwhite_yuv444p-frame.hevc 444.yuv -v debug

FFmpeg configuration:

% ffmpeg version n6.0.1 Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 10 (Debian 10.2.1-6)
  configuration: --prefix=/home/mou/Documents/Dev/FFmpeg/build
  libavutil      58.  2.100 / 58.  2.100
  libavcodec     60.  3.100 / 60.  3.100
  libavformat    60.  3.100 / 60.  3.100
  libavdevice    60.  1.100 / 60.  1.100
  libavfilter     9.  3.100 /  9.  3.100
  libswscale      7.  1.100 /  7.  1.100
  libswresample   4. 10.100 /  4. 10.100

OS information:

%        _,met$$$$$gg.          mou@debianMou 
    ,g$$$$$$$$$$$$$$$P.       ------------------------ 
  ,g$$P"     """Y$$.".        OS: Debian GNU/Linux 11 (bullseye) x86_64 
 ,$$P'              `$$$.     Host: Prestige 14 A11SCS REV:1.0 
',$$P       ,ggs.     `$$b:   Kernel: 5.10.0-26-amd64 
`d$$'     ,$P"'   .    $$$    Uptime: 5 hours, 6 mins 
 $$P      d$'     ,    $$P    Packages: 3503 (dpkg), 8 (flatpak) 
 $$:      $$.   -    ,d$$'    Shell: zsh 5.8 
 $$;      Y$b._   _,d$P'      Resolution: 1920x1080, 2560x1440 
 Y$$.    `.`"Y$$$$P"'         DE: Plasma 5.20.5 
 `$$b      "-.__              WM: KWin 
  `Y$$                        WM Theme: Breeze 
   `Y$$.                      Theme: Breeze Dark [Plasma], Breeze [GTK2/3] 
     `$$b.                    Icons: breeze-dark [Plasma], breeze-dark [GTK2/3] 
       `Y$$b.                 Terminal: yakuake 
          `"Y$b._             CPU: 11th Gen Intel i7-1165G7 (8) @ 4.700GHz 
              `"""            GPU: NVIDIA GeForce GTX 1650 Ti Mobile 
                              GPU: Intel TigerLake GT2 [Iris Xe Graphics] 
                              Memory: 5889MiB / 15697MiB 

[kebs00n]

console output logs

[kebs00n]

vainfo output

[kebs00n]

444 HEVC video frame sample

[Jun Zhao]

If my memory is correct, VAAPI does not support the YUV444 format

[Fei Wang]

You may need to update your VAAPI/media-driver version. HEVC 444 supported after VAAPI 1.2.0.

[Balling]

You may need to update your VAAPI/media-driver version. HEVC 444 supported after VAAPI 1.2.0.

reopen if it still happens on new intel driver.