[Libav-user] hwaccel and the new API

wm4 nfxjfg at googlemail.com
Tue Dec 1 15:33:02 CET 2015

On Tue, 6 Oct 2015 14:01:17 -0700
Ratin <ratin3 at gmail.com> wrote:

> I have seen some changes regarding hwaccel part of libav/ffmpeg API and
> after adopting to minimal set of changes, my app stopped working
> assertion src->f->buf[0] failed at libavcodec/h264_picture.c:73
> Program received signal SIGABRT, Aborted.
> I noticed the alloc rotines are updated, is the AVFrame->data[0] and
> AVFrame->data[3] still the containers for HW allocated surface struct
> pointer and surface ID respectively?

Yes, but you are required to allocate refcounted frames in your
get_buffer2 callback. Which involves setting buf[0] to something

More information about the Libav-user mailing list