[Ffmpeg-devel] New/extended filter API discussion

[Jason Tackaberry]

On Fri, 2007-01-05 at 20:52 +0100, Michael Niedermayer wrote:
> to repeat again some goals of a video filter API
> * well documented (see mplayer for how not to do it)
> * writing a filter should not require complete knowledge of all
>   (undocumented) internals of the video filter system
> * direct rendering (useing a buffer provided by the next filter)
> * inplace rendering (for example adding some subtitles shouldnt need the
>   whole frame to be read and written)
> * slices based rendering (improves cache locality, but there are issues
>   with out of order decoding ...)
> * multiple inputs
> * multiple outputs (could always trivially be handled by several filters
>   with just a single output each)
> * timestamps per frame
> * also th number of frames consumed by a filter does not have to match the
>   number output ((inverse)telecine, ...)

Every single bullet on this list is supported by Xine's post plugin
architecture, so someone doing the design may want to look there for
inspiration.

Cheers,
Jason.