[FFmpeg-devel] [PATCH] Per-frame metadata
stefano.sabatini-lala at poste.it
Tue Apr 12 22:02:40 CEST 2011
On date Tuesday 2011-04-12 20:38:18 +0200, Alexander Strasser encoded:
> Nicolas George wrote:
> > Le tridi 23 germinal, an CCXIX, Stefano Sabatini a écrit :
> > > Nit: multiply
> > Fixed locally.
> > > -1 -> AVERROR(EINVAL)
> > That require mem.h to include error.h, and this is the only conceivable
> > error for av_size_mult, so I am mildly in favor of keeping -1. But if you
> > insist on AVERROR(EINVAL) I will change.
> > > Would it make sense to move metadata to libavutil rather than to
> > > libavcodec?
> > >
> > > For example you may need to display metadata from a lavfi filter.
> > libavutil was my first choice, as it has absorbed libavcore; but Michael
> > seemed to prefer libavcodec.
> > If you think this is better in libavutil I will make the change.
> Just for the record:
> I still dislike the merge of libavcore into libavutil and I dislike
> adding more stuff on top of that, too.
> There should be better solutions like making lavfi purposefully
> depend on lavc or something I didn't yet think of.
Of course this is possible, but I also want to keep the dependencies
of lavfi as low as possible, also logically metadata doesn't seem
related to (only) codecs.
> I know this has its drawbacks as well, but maybe something can be
> done about it.
If you want to keep lavu small, there is still the possibility to make
it modular, and strip whatever is not needed through some configure
magic, possibly unsafe (from the ABI/API compatibility standpoint) but
should work fine for self-contained projects with very strict
footprint requirements (e.g. micro-devices).
FFmpeg = Funny and Frenzy Multimedia Puristic Evanescent Gadget
More information about the ffmpeg-devel