[Ffmpeg-devel] Port MPlayer's vf to FFMpeg (was [PATCH] enable libswscale)

Rich Felker dalias
Thu Sep 14 17:38:44 CEST 2006


On Thu, Sep 14, 2006 at 04:49:01PM +0200, Michael Niedermayer wrote:
> Hi
> 
> On Thu, Sep 14, 2006 at 04:22:35PM +0200, Diego Biurrun wrote:
> > On Thu, Sep 14, 2006 at 04:18:33PM +0200, Michael Niedermayer wrote:
> > > 
> > > On Thu, Sep 14, 2006 at 02:06:32PM +0200, V?ctor Paesa wrote:
> > > > 
> > > > >>
> > > > >> well, my idea was to change the vfilter realated files from libmpcodecs
> > > > >>so
> > > > >> they can be compiled as an independant lib to which then mplayer and
> > > > >> ffmpeg
> > > > >> could link, ripping all the vf* out and dropping them (with
> > > > >modifictaions)
> > > > >> in ffmpeg would be less optimal as someone would have to maintain,
> > > > >update,
> > > > >> ...
> > > > >> this libmpcodecs fork for "eternity"
> > > > >
> > > > 
> > > > > Why?  MPlayer could use it from FFmpeg then, couldn't it?
> > > 
> > > iam against moving libmpcodecs into ffmpeg svn
> > 
> > Why?  Due to Subversion technical shortcomings or other reasons?
> 
> well there are many reasons
> * there are surely the technical issues with SVN
> * libmpcodecs are (audio, video) X (filters, decoders, encoders)
>   in many cases these are wrapers for mplayer they belong to mplayer and
>   not ffmpeg, so ill assume that this disscussion is just about the video
>   filters
> * rich wanted to design a better filter system for ffmpeg ...
>   whats the staus of that?
> * whats the oppinion of the other mplayer developers about that?

Regardless of whether I or someone else designs a better system, the
MPlayer vf system is so bad that it absolutely does not belong in the
ffmpeg framework. It would just make the code horribly
ugly/broken/unmaintainable. Not to mention the vf system does not
support lavc's idea of buffer handling whatsoever, and presently the
pts support is highly lacking.

Rich





More information about the ffmpeg-devel mailing list