On Fri, Oct 26, 2018 at 4:00 PM James Almer <jamr...@gmail.com> wrote:
> On 10/26/2018 7:50 PM, Dale Curtis wrote: > > One more piece of feedback, this is not obeying the > > AVCodecContext.get_buffer2 API. > > It's not using it on purpose, wrapping the buffers dav1d allocated > itself instead. Hence the lack of AV_CODEC_CAP_DR1 flag. > Sorry for being unclear, my comment was a request. This is something Chromium would require to use this wrapper. If it's not planned, we'd forgo the wrapper and use dav1d directly. Otherwise we'd need to change our common ffmpeg based decoder enough for this one case that we'd be better off writing a pure dav1d based decoder. Thanks for your consideration in any case. - dale _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
