[FFmpeg-devel] [PATCH v2 3/8] lavc: introduce a new decoding/encoding API with decoupled input/output

Carl Eugen Hoyos cehoyos at ag.or.at
Wed Mar 23 14:45:21 CET 2016


wm4 <nfxjfg <at> googlemail.com> writes:

> 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.

Is the new API supposed to have a performance impact?

Or is it just simpler than the existing one?
(Is it simpler?)

Thank you, Carl Eugen



More information about the ffmpeg-devel mailing list