Re: [libav-devel] [PATCH 1/9] lavc: Add codec metadata to indicate hardware support

On Fri, 27 Oct 2017 12:37:18 +0100 Mark Thompson wrote: > >> Can you suggest the sort of names you're thinking of here? I think this > >> might depend on (3) as well to be useful. > > > > I was thinking maybe "hwaccel_vaapi" etc. > > I feel like this sort of name is

Re: [libav-devel] [PATCH 1/9] lavc: Add codec metadata to indicate hardware support

On 26/10/17 13:56, wm4 wrote: > On Thu, 26 Oct 2017 13:27:01 +0100 > Mark Thompson wrote: > >> On 26/10/17 11:36, wm4 wrote: >>> On Thu, 26 Oct 2017 00:18:39 +0100 >>> Mark Thompson wrote: >>> --- Rebased on the frame parameter changes, and

Re: [libav-devel] [PATCH 4/9] webp: Fix alpha initialisation

On 26/10/17 08:27, Diego Biurrun wrote: > On Thu, Oct 26, 2017 at 12:18:42AM +0100, Mark Thompson wrote: >> ff_get_format() in the next patch will reject formats which aren't in the >> offered list, so the hack in 7cb9296db872c4221453e5411f242ebcfca62664 is >> no longer valid. Change the hack by

Re: [libav-devel] [PATCH 2/9] lavc: Add a new file listing all hwaccels as external declarations

On 26/10/17 08:26, Diego Biurrun wrote: > On Thu, Oct 26, 2017 at 12:18:40AM +0100, Mark Thompson wrote: >> These will be used later to generate the hwaccel list at configure time, >> but are needed now for the config structures in the following patch. >> --- >> libavcodec/hwaccels.h | 59 >>