[FFmpeg-trac] #10374(avcodec:new): Problems to decode certain h264 keyframes with D3D11VA and DXVA2 hw acceleration

FFmpeg trac at avcodec.org
Fri May 19 22:54:52 EEST 2023


#10374: Problems to decode certain h264 keyframes with D3D11VA and DXVA2 hw
acceleration
-------------------------------------+-------------------------------------
             Reporter:  Florian      |                    Owner:  (none)
  Grill                              |
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  avcodec
              Version:  6.0          |               Resolution:
             Keywords:  H264 dxva2   |               Blocked By:
  d3d11va                            |
             Blocking:               |  Reproduced by developer:  1
Analyzed by developer:  1            |
-------------------------------------+-------------------------------------
Comment (by Florian Grill):

 Hmm, so what to do? Let's keep h264 DXVA2 and D3D11VA decoder broken?
 Funny thing is software decoding works and doesn't care about this
 limitation. I already showed where the limit is used in dxva2_h264.c, so
 why is dxva2_h264 just not overriding this limit like the dxva2_hevc
 decoder for example? What actually is the advantage of such a small slice
 limit and why is this limit throttling the capability of the h264 DXVA2
 and D3D11VA decoder? Sorry I just don't understand the reason behind it.
 The MAX_SLICES value is maybe a good default value but there is no way to
 override this from an application point of view, which leads to the fact
 that the h264 DXVA2 and D3D11VA decoder can't be used if the user is
 dealing with a stream which contains key frames with slices bigger than
 32.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/10374#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list