[FFmpeg-trac] #7839(avcodec:new): QVBR breaks mpeg2_qsv

[FFmpeg]

#7839: QVBR breaks mpeg2_qsv
-------------------------------------+-------------------------------------
             Reporter:  atorp        |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  important    |                Component:  avcodec
              Version:  git-master   |               Resolution:
             Keywords:  qsv          |               Blocked By:
  regression                         |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by lizhong1008):

 Replying to [comment:9 atorp]:
 > > Probably it is that your MSDK version can't support coding option 3.
 >
 >
 > I don't know it! I'm using Windows 10 with the last Intel drivers
 installed. And the binaries are the "zeranoe".

 You can find it with a pure qsv HW transcoding pipeline:
 ffmpeg -hwaccel qsv -v verbose -c:v h264_qsv -i input_h264.mp4 -c:v
 mpeg2_qsv test_qsv.mp4
 On my side, I see can the log:
 Initialize MFX session: API version is 1.28, implementation version is
 1.29
 Could you please report what the log on your side to me?

 > Replying to [comment:8 lizhong1008]:
 >
 > > 1. Could you please tell me what is your MSDK API version and library
 version.
 > > 2. Apply the patch:
 > > -#define QSV_HAVE_CO3 QSV_VERSION_ATLEAST(1, 11)
 > > +#define QSV_HAVE_CO3 0
 > > Don't change anything else.
 > > 3. If it is possible, update your MSDK version can try again.
 >
 >
 > I'll do more tests. But, your suggestion of patch is already included in
 my previous fix! But it disables at all QVBR.
 Your previous fix disale two things: both CO3 and QVBR, what is the exact
 one can fix this problem? CO3 or QVBR, or must disable all of the two?

 > In any case, please try it on Windows.

 Sorry, I have no Windows qsv environment now.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/7839#comment:11>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker