On Mon, Mar 21, 2016 at 01:40:11PM +0000, Mark Thompson wrote:
> On 21/03/16 13:02, Diego Biurrun wrote:
> > On Mon, Mar 21, 2016 at 12:47:46PM +0000, Mark Thompson wrote:
> >> Referring back to a previous response, can you offer any guidance about 
> >> how you
> >> think the "vaapi", "vaapi_encode" etc. config options should be arranged?
> >> (Including replacing existing "vaapi" with "vaapi_decode", I think.)
> >
> > Sorry, I'm missing context here.  Could you please reply to that other
> > response to help jog my failing memory?
> 
> Below.
> 
> Meanings being something like:
> 
> VAAPI: hwcontext support, avconv, scale filter.
> VAAPI_DECODE: decode support, hwaccels.
> VAAPI_ENCODE: encode support, encoder instances.
> 
> (Maybe avconv should be some other combination; currently it requires X11 or 
> DRM
> to actually work (it can't get a device handle without one of those), though
> they aren't build dependencies.)

Sounds good.

Diego
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to