On Tue, 19 Apr 2016 11:49:11 +0200 wm4 <nfx...@googlemail.com> wrote:
> Until now, the decoding API was restricted to outputting 0 or 1 frames > per input packet. It also enforces a somewhat rigid dataflow in general. > > This new API seeks to relax these restrictions by decoupling input and > output. Instead of doing a single call on each decode step, which may > consume the packet and may produce output, the new API requires the user > to send input first, and then ask for output. > > For now, there are no codecs supporting this API. The API can work with > codecs using the old API, and most code added here is to make them > interoperate. The reverse is not possible, although for audio it might. > > From Libav commit 05f66706d182eb0c36af54d72614bf4c33e957a9. > > Signed-off-by: Anton Khirnov <an...@khirnov.net> > --- > This commit was skipped when merging from Libav. > --- Pushed, with review suggestions applied, lavc minor version bumped, and patch 2 squashed into 1. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
