Hello,
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.
Sincerely,
Tuukka
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: https://blogs.gentoo.org/lu_zero/2016/03/29/new-avcodec-api/
On Thu, Oct 20, 2016 at 6:13 AM, Chao Liu <[email protected]
<mailto:[email protected]>> wrote:
Hi,
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
[email protected] <mailto:[email protected]>
http://ffmpeg.org/mailman/listinfo/libav-user
<http://ffmpeg.org/mailman/listinfo/libav-user>
--
Shu. Wang @ Bestminr
http://halfelf.me
_______________________________________________
Libav-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/libav-user
_______________________________________________
Libav-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/libav-user
