[FFmpeg-trac] #3133(avcodec:open): Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC

[FFmpeg]

#3133: Incompatibilities beween ffmpeg 2.0.2 and 2.1 exposed via XBMC
-------------------------------------+-------------------------------------
             Reporter:  EricV        |                    Owner:
                 Type:  defect       |                   Status:  open
             Priority:  important    |                Component:  avcodec
              Version:  git-master   |               Resolution:
             Keywords:  vdpau        |               Blocked By:
  regression                         |  Reproduced by developer:  0
             Blocking:               |
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by cehoyos):

 Just a few comments not strictly related to this problem:
 MPlayer uses internal FFmpeg since forever, binaries with external FFmpeg
 are not supported afaict (or as far as I am concerned), but MPlayer always
 uses current FFmpeg git head (meaning it receives not only new features
 but also bug fixes - including security relevant ones)

 Random old snapshots are bound (and known) to contain bugs (including
 regressions and security relevant issues), if you cannot use current git
 head at the time of a xbmc release (why not?) then I strongly suggest to
 use at least a current release series (2.1 and very soon 2.2), releases
 get regression and security fixes later but they get them.

 Note that if you have local patches that you need in FFmpeg, please
 propose them on ffmpeg-devel (yes, the policy has changed).

 There will be no further releases in the 2.0 branch, note that it does
 contain known bugs.

 I don't know why the "new" vdpau code was changed, I only feel responsible
 for the old code (which was extensively tested with tools that we do not
 have access to and could not be used when the "new" code was committed!),
 both work with MPlayer, both are tested regularly with MPlayer.

 Strictly related to this ticket:
 I would suggest that you locally revert the offending commit in the
 release/2.1 branch and test, I will commit such a change to the FFmpeg
 repository.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3133#comment:62>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker