[FFmpeg-devel] Integrating the mod engine into FFmpeg - what is the best design approach?
Sat Jul 17 15:00:59 CEST 2010
On Sat, Jul 17, 2010 at 07:41:35PM +1000, Peter Ross wrote:
> On Sat, Jul 17, 2010 at 10:07:43AM +0200, Michael Niedermayer wrote:
> > On Sat, Jul 17, 2010 at 03:04:17PM +1000, Peter Ross wrote:
> > > On Fri, Jul 16, 2010 at 04:15:26PM +0200, Vitor Sessak wrote:
> > > > On 07/16/2010 03:46 PM, Sebastian Vater wrote:
> > > > >Hello dears!
> > > > >
> > > > >I had a discussion with Vitor and Stefano about the best way to
> > > > >integrate the mod engine into FFmpeg.
> > >
> > > > >I see just one disadvantage here, simply extraction of metadata and
> > > > >removing it, passing the rest to AVPacket requires parsing of all module
> > > > >files twice and also manipulating them (correct the offsets, etc.). This
> > > > >would require duplicate code in the demuxer and decoder, which I would
> > > > >like to avoid, if possible.
> > >
> > > The same problem exists for image metadata. Simple solution would be
> > > to permit codecs to get and set metadata.
> > id like to point out that i wanted AVMetadata in lavc when it was written
> > already but people where against it.
> > so maybe its time to move it over ...
> I feel that this should not hold up Sebastian's project.
i did not suggest that it should
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
In a rich man's house there is no place to spit but his face.
-- Diogenes of Sinope
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
More information about the ffmpeg-devel