[Libav-user] Frames corruption when seeking...
nfxjfg at googlemail.com
Sat May 31 14:40:09 CEST 2014
On Sat, 31 May 2014 13:15:19 +1000
Jean-Yves Avenard <jyavenard at gmail.com> wrote:
> On 31 May 2014 02:58, Carl Eugen Hoyos <cehoyos at ag.or.at> wrote:
> > Then allow me to rephrase:
> > If you have a H264 sample that allows seeking to a
> > non-keyframe (so that you see artefacts), please
> > provide it.
> You don't seem to have read the entire discussion.
> I've never even suggested there was an issue in libav*, but in my
> usage of it as I had no issue before, and I'm having issue now.
> So I was only inquiring if there was anything that had been changed in
> the FFmpeg API that could explain what was going on.
> Having said that, after remove most of the call to functions marked as
> deprecated, I'm not seeing any issue anymore.
> This now leads me to believe the issue is within the old API...
It's certainly possible that the old API is either already broken, or
easily breaks when combining with new API.
> Moving to the new AVFrame structure and get_buffer2() will require
> significant change to our code and architecture...
> Hopefully, get_buffer() and release_buffer() won't be removed anytime soon..
get_buffer2 isn't _that_ different. Just instead of release_buffer, you
have to set the destruction callback on the AVBuffer you use for the
AVFrame returned with get_buffer2.
More information about the Libav-user