On Thu, Dec 11, 2014 at 01:22:28AM +0000, Vittorio Giovara wrote: > On Tue, Dec 9, 2014 at 10:15 PM, wm4 <nfx...@googlemail.com> wrote: > > On Tue, 9 Dec 2014 21:33:41 +0100 > > Reimar Döffinger <reimar.doeffin...@gmx.de> wrote: > > > >> On Tue, Dec 09, 2014 at 12:59:24PM +0000, Vittorio Giovara wrote: > >> > On Tue, Dec 9, 2014 at 8:04 AM, wm4 <nfx...@googlemail.com> wrote: > >> > > On Tue, 9 Dec 2014 02:57:01 +0100 > >> > > Michael Niedermayer <michae...@gmx.at> wrote: > >> > > > >> > > It seems very wrong to export this info optionally just because > >> > > ffmpeg.c is too stupid to handle it correctly. > >> > > >> > Not exporting saves a little bit of memory too, since you have to > >> > allocate the space where to export this metadata to too. > >> > We're often talking about more than hundreds of megabytes. > > > > WTF, > 100 MBs of XML? In media files? > > Yep, it's not uncommon that xmp contains the all the save states of > the project files (eg the list of undo action), imports, outputs > proxies and other stuff. It gets to ridiculous dimensions pretty > quickly. > > >> From that aspect it might make more sense to have a generic > >> option to not export metadata larger than a certain size for example. > >> Or some other system. > > > > Until now, the method for exporting large metadata-like blobs was > > adding new streams. E.g. picture attachments and fonts. > > That would be neat. Until then, can we have this patch committed?
applied i hope this is what most prefer [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No snowflake in an avalanche ever feels responsible. -- Voltaire
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel