Bug#879673: ffmpeg 3.4 API compat layer not 100% backwards compatible

[James Cowgill]

Control: forwarded -1 https://trac.ffmpeg.org/ticket/6775
Control: tags -1 upstream

Hi,

On 24/10/17 09:52, Sebastian Dröge wrote:
> Package: ffmpeg
> Version: 7:3.4-1
> Severity: serious
> 
> Hi,
> 
> ffmpeg 3.4 comes with a new decoding API (among other things), and
> provides a compatibility layer around that for the old API.
> Unfortunately this compatibility layer is apparently not 100% backwards
> compatible or buggy. It breaks at least h264 decoding with gst-
> libav1.0, but then probably also breaks other packages.

The new decoding API was introduced in 3.1. The change in 3.4 was to
have the old API call into the new API instead of the other way around.

> gst-libav upstream bug can be found here:
> https://bugzilla.gnome.org/show_bug.cgi?id=789193

OK, hopefully upstream ffmpeg can help fixing this bug, since I'm not
sure what I can do about it.

> We'll try to port over to the new API but it looks like some effort,
> and even independent of that the compatibility layer should either be
> fixed or the soname of the libraries has to be updated.

Updating SONAMEs doesn't help when there's an API break and the behavior
of existing functions has changed.

Thanks,
James

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20171024/72531eeb/attachment.sig>