[FFmpeg-trac] #8902(avcodec:new): VAAPI pixel format support regression between FFmpeg 3.x and 4.x

FFmpeg trac at avcodec.org
Wed Feb 3 12:42:16 EET 2021

#8902: VAAPI pixel format support regression between FFmpeg 3.x and 4.x
             Reporter:  bmegli       |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  avcodec
              Version:  git-master   |               Resolution:
             Keywords:  vaapi        |               Blocked By:
  regression                         |
             Blocking:               |  Reproduced by developer:  1
Analyzed by developer:  0            |

Comment (by bmegli):

 Thank you.

 >  I think the "[AVHWDeviceContext @ 0x55dcc90cf7e0] Format 0x32315659 ->"
 means the pixel format supported by libva and the pixel format that can be
 encoded by h264 is a subset of them, because libva can also do video

 From the user perspective, in 3.x the conversion happened automatically
 (probably by libva or below).

 1. Do you know if libva conversions are hardware or software?

 From my user perspective using this path was like "let the hardware
 interface decide the optimal execution path", maybe it works with this
 kind of surface, maybe it performs additional software conversion on the

 > In 4.x version, you may need to do the pixel format transformation
 manually. You can use sws_scale or "hwupload" filter to do this.

 Sure, I am aware of those possibilities.

 sws_scale will result in (hardcoded) software conversion on the way.

 So "hwupload" may be the possibility to recreate behavior from 3.x
 (performing conversion through libva whatever that means in the end).

Ticket URL: <https://trac.ffmpeg.org/ticket/8902#comment:5>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list