[Libav-user] New encoding / decoding API
yijinliu at gmail.com
Sat Oct 22 01:29:28 EEST 2016
On Thu, Oct 20, 2016 at 5:59 AM, Tuukka Pasanen <pasanen.tuukka at gmail.com>
> Just wondering is this new decode/encode system here to stay? If it is all
> examples should be upgraded as I used ffplay to see how to make it work
> (Use the source) but it shouldn't be like that. codepar is easiest to adapt
> but lot of old code is going to get obsolete soon.
I don't see why not.. I like the new decode / encode API. I have a camera
which produces packets containing multiple frames. w/o this change I have
to hack the AVPacket structure after decoding, which is ugly and
The new API deals with this problem decently.
> 20.10.2016, 06:03, Shu Wang kirjoitti:
> Hi Liu,
> *codec -> codecpar* isn't a big change, and is easy to upgrade. Clone
> and pull the snapshot repo, you'll see some examples has been updated,
> though not all of them.
> While the new decode/encode API is another story. I haven't tried these
> yet. Not many examples I can find. Maybe the closest one is this:
> On Thu, Oct 20, 2016 at 6:13 AM, Chao Liu <yijinliu at gmail.com> wrote:
>> I am trying to upgrade our code to 3.1. There are a lot of warnings about
>> deprecated APIs, like use AVStream.codecpar instead of AVStream.codec,
>> use avcodec_send_packet()/avcodec_receive_frame() instead
>> of avcodec_decode_video2. Are there any examples how to do the transition?
>> I noticed that all these examples
>> <https://www.ffmpeg.org/doxygen/3.1/examples.html> are still using the
>> old APIs. Should they be updated?
>> Libav-user mailing list
>> Libav-user at ffmpeg.org
> Shu. Wang @ Bestminr
> Libav-user mailing listLibav-user at ffmpeg.orghttp://ffmpeg.org/mailman/listinfo/libav-user
> Libav-user mailing list
> Libav-user at ffmpeg.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libav-user