[FFmpeg-trac] #4831(avcodec:reopened): Can't initialize h264_qsv encoder post Aug 29 2015 - Ivy Bridge CPU

[FFmpeg]

#4831: Can't initialize h264_qsv encoder post Aug 29 2015 - Ivy Bridge CPU
-------------------------------------+-------------------------------------
             Reporter:  babgvant     |                    Owner:  IvUs
                 Type:  defect       |                   Status:  reopened
             Priority:  important    |                Component:  avcodec
              Version:  git-master   |               Resolution:
             Keywords:  qsv          |               Blocked By:
  regression                         |  Reproduced by developer:  0
             Blocking:               |
Analyzed by developer:  1            |
-------------------------------------+-------------------------------------

Comment (by babgvant):

 After a certain point (2yrs IIRC) Intel doesn't update the MSDK version in
 the latest driver. So while they may release a new driver to fix a
 critical issue for an IVB (which has pretty good h.264 encoding support)
 they won't update it to the latest MSDK, so it's frozen forever at this
 level.

 I totally agree that flipping the min level recompiling isn't a good
 option. I think that (like every MSDK supporting app that I'm aware of)
 ffmpeg should query the MSDK level and selectively enable/configure
 features based on it (which might be what you're saying as well).

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