[Ffmpeg-devel] plug-n-play codecs support

[Kid OnTheWay]

yes, 

I also thinks that depenencies are there, but all are related.
Although I have checked this only for H.264, I found that much of the
coe in other files are not affecting it at all. Bulk of it is h264 and
mpegvideo.c itself. rest utils file are common to all.

It may not be tough to separate them. IMHO :-) but i am still a Kid.

regards
Kid

On 4/30/05, Michael Niedermayer <michaelni at gmx.at> wrote:
> Hi
> 
> On Saturday 30 April 2005 11:19, Arpi wrote:
> > Hi,
> >
> > > M?ns Rullg?rd wrote:
> > > > Aaron Lee <waifunlee at gmail.com> writes:
> > > > > I would like to build a ffmpeg dynamic loading mechanism such that
> > > > > codecs can be built as a dll and be loaded at runtime rather than
> > > > > statically bundle all codecs in a big library. Has anyone done that
> > > > > before?
> > > >
> > > > Many of the codecs share the core components, only the bit parsing
> > > > being specific.  This means that the cost of each codec isn't as high
> > > > as it might seem.
> > >
> > >   In addition i think it would be way more useful to make the codecs
> > > selectable at compile time which is in the works if i understood
> >
> > the problem(?) is that they share a lot more.
> > try to remove a codec file from Makefile, and see how many other
> > codecs use some code from it. the libavcodec codecs has a lot
> > cross-dependency on eachother, sharing small helper functions or
> > sometimes even big parsers (with some if()'s inside to check codec type).
> 
> i think you overestimate the dependencies, AFAIK, the dependencies should be
> mostly sane like that h263 based codecs need h263*.{c,h} dct/MC based codecs
> need mpegvideo.{c,h}
> 
> [...]
> 
> --
> Michael
> 
> "nothing is evil in the beginning. Even Sauron was not so." -- Elrond
> 
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at mplayerhq.hu
> http://mplayerhq.hu/mailman/listinfo/ffmpeg-devel
>