On Mon, 18 Aug 2014 11:44:01 -0700, Andrew Kelley <[email protected]> wrote: > On Mon, Aug 18, 2014 at 11:04 AM, Anton Khirnov <[email protected]> wrote: > > > +One specific API issue in libavformat deserves mentioning here. When the > > calling > > +code uses libavcodec for decoding or encoding and libavformat for > > +demuxing/muxing, the standard practice was to use the stream codec context > > +(AVStream.codec) for actual decoding or encoding. There are multiple > > problems > > +with this pattern (the main one is that the decoder/demuxer or > > encoder/muxer are > > +not necessarily synchronized and may overwrite each other's state), so it > > is now > > +strongly discouraged and will likely be deprecated in the future. The > > users > > +should instead allocate a separate decoding or encoding context and > > populate it > > +from the demuxing codec context (or the reverse for encoding) with the > > +avcodec_copy_context() function. > > > Is there an example commit somewhere which demonstrates updating code for > this new API?
There is one for avconv, but it's a bit too large to be a good example. I'm planning to update the output example, but didn't get to that yet. -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
