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

2017-11-09 Thread James Cowgill
Control: clone -1 -2 -3 Control: reassign -2 gst-libav1.0 1.12.3-1 Control: notforwarded -2 Control: severity -2 important Control: affects -2 - src:kodi src:gst-libav1.0 Control: retitle -2 gst-libav1.0: incorrect use of drain packets in avcodec_decode_* api Control: reassign -3 kodi

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

2017-11-07 Thread James Cowgill
Control: affects -1 src:kodi src:gst-libav1.0 Control: tags -1 patch 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

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

2017-10-24 Thread Sebastian Dröge
On Tue, 2017-10-24 at 13:44 +0100, James Cowgill wrote: > > 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. It seems like it also introduces

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

2017-10-24 Thread 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

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

2017-10-24 Thread Sebastian Dröge
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