On Fri, 26 Jan 2018 23:30:48 +0000 Mark Thompson <[email protected]> wrote:
> On 26/01/18 23:13, Mark Thompson wrote: > > AVFilterContext.extra_hw_frames functions identically to the field of > > the same name in AVCodecContext. > > Of course, that field doesn't actually exist before this patch now. Updated > to reflect that. > > Still, should the field be in AVCodecContext as well? (The > hw_frames_parameters API can do this for library users, but it isn't usable > in avconv.) Probably makes sense. How else would avconv control this? (Although in theory avconv could use the avcodec_get_hw_frames_parameters() API.) I assume actually this field would just be added to the frames context returned by avcodec_get_hw_frames_parameters(), since that is used internally by most hwaccels to allocate a frames context if hw_device_ctx is used. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
