On Thu, Feb 19, 2015 at 06:26:16PM +0000, Kevin Wheatley wrote: > Hi, > > I realise this potentially breaks through lots of API boundaries/good > taste, but I've noticed a case where the movenc.c code should really > ask the specific encoder context (DNXHDEncContext) for some of it's > fields to ensure that the atoms written have a consistent setting with > what the codec did. > > Is this something 'allowed'? How best should I access it?
theres no encoder, the data could instead come from another mov file or a binary encoder used by some user application with libavformat [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No great genius has ever existed without some touch of madness. -- Aristotle
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
