[FFmpeg-devel] [libav-devel] [PATCH 0/20] removal of deprecated features

Reimar Döffinger Reimar.Doeffinger at gmx.de
Sat Aug 1 09:41:56 CEST 2015

On 30.07.2015, at 17:05, Andreas Cadhalpun <andreas.cadhalpun at googlemail.com> wrote:
> Hi,
> On 28.07.2015 15:36, Vittorio Giovara wrote:
>> This set contains the removal of all deprecated features marked as
>> such until 2012/early 2013. This was announced several times in the
>> past months and agreed at several meetings (since fosdem and recently
>> at the sprint).
>> With more than two year span, downstream users should have had enough
>> time to update their API usage (or comment otherwise).
> Unfortunately this is just wishful thinking.
> As it is, your proposed removal of deprecated features is going to break
> about three quarters of all packages using the libav* libraries in Debian:
> amide avbin avifile bino chromium-browser dff dolphin-emu dvswitch
> ffmpeg2theora ffmpegthumbnailer ffmpegthumbs fuse-emulator-utils
> gmerlin-avdecoder gmerlin-encoders gnash gpac gst-libav1.0 guvcview harvid
> hedgewars info-beamer karlyriceditor kodi lebiniou libam7xxx libavg libde265
> libextractor libquicktime linphone lives lynkeos.app mlt mplayer mplayer2 opal
> openscenegraph ovito paraview performous pjproject qutecom rbdoom3bfg sflphone
> strigi survex transcode vtk vtk6 vxl wxsvg x264 xjadeo xpra yorick-av
> zoneminder
> acoustid-fingerprinter amarok aubio blender chromaprint dvbcut gazebo
> goldendict jugglemaster kino lightspark mrpt opencv shotdetect spek
> squeezelite vcmi vlc xine-lib-1.2
> alsa-plugins cantata ffdiaporama moc mpv
> openmw
> pianobar
> Note that this is only counting one API per packet.

Hm, so all those PIX_FMT cases might hide a lot of other issues?
I think that one isn't a real issue as it hardly has any maintenance cost (I think I fixed MPlayer now though).
Can we potentially get lists for each, to see if we can put pressure on certain projects so we can get rid of the worst?

> Considering how widespread the use of FF_API_PIX_FMT and FF_API_AVFRAME_LAVC
> still is, it might make sense to delay their removal.

If the list was complete, I wouldn't say AVFRAME is that widespread, a bit of pushing might work still...

More information about the ffmpeg-devel mailing list