Quoting Diego Biurrun (2016-12-06 23:20:45)
> On Sat, Dec 03, 2016 at 05:34:34PM +0100, Anton Khirnov wrote:
> > --- /dev/null
> > +++ b/libavcodec/hwaccel.h
> > @@ -0,0 +1,24 @@
> > +#ifndef AVCODEC_HWACCEL_H
> > +#define AVCODEC_HWACCEL_H
> > +
> > +#define HWACCEL_CAP_ASYNC_SAFE (1 << 0)
>
On Sat, Dec 03, 2016 at 05:34:34PM +0100, Anton Khirnov wrote:
> --- /dev/null
> +++ b/libavcodec/hwaccel.h
> @@ -0,0 +1,24 @@
> +#ifndef AVCODEC_HWACCEL_H
> +#define AVCODEC_HWACCEL_H
> +
> +#define HWACCEL_CAP_ASYNC_SAFE (1 << 0)
> +
> +#endif /* AVCODEC_HWACCEL_H */
Do you plan to add
On 2016-12-03 17:34:34 +0100, Anton Khirnov wrote:
> Certain hardware decoding APIs are often not thread-safe, so having the user
> access decoded hardware surfaces while the decoder is running in another
> thread can cause failures (this is mainly known to happen with DXVA2).
>
> For such
Certain hardware decoding APIs are often not thread-safe, so having the user
access decoded hardware surfaces while the decoder is running in another
thread can cause failures (this is mainly known to happen with DXVA2).
For such hwaccels, only allow the decoding thread to run while the user
is
