On Sat, Dec 03, 2016 at 12:57:49AM +0100, Hendrik Leppkes wrote: > On Sat, Dec 3, 2016 at 12:52 AM, Michael Niedermayer > <mich...@niedermayer.cc> wrote: > > This is a bit messy as codecar does not support AVOptions so we need > > to use AVCodecContext where AVOptions are required and copy back and forth. > > >
> ffmenc can't really write any data that doesn't go into codecpar > either, since thats all muxers get for stream info, so is this really > required? Where do these come from? ffmenc takes the string from AVStream.recommended_encoder_configuration and stores it, ffmdec reads it back into AVStream.recommended_encoder_configuration It is just needed to make sure codecpar matches this, which would be easier if AVOptions would work with codecpar as then it could be directly set from the string description. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
