On Sun, 26 Apr 2020 at 19:54, Mark Thompson wrote:
> On 24/04/2020 15:52, artem.ga...@gmail.com wrote:
> > From: Artem Galin
> >
> > Makes selection of d3d11va device type by default and over DirectX 9,
> > which is still supported but requires explicit selection.
>
> ... which might break users
On Sun, Apr 26, 2020 at 10:00 PM Soft Works wrote:
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Mark Thompson
> > Sent: Sunday, April 26, 2020 8:54 PM
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: Re: [FFmpeg-devel] [PATCH v3 4/
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Mark Thompson
> Sent: Sunday, April 26, 2020 8:54 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v3 4/4] libavutil/qsv: enabling d3d11va
> support
>
> On 24/04/2020 15:52,
On 24/04/2020 15:52, artem.ga...@gmail.com wrote:
> From: Artem Galin
>
> Makes selection of d3d11va device type by default and over DirectX 9,
> which is still supported but requires explicit selection.
... which might break users with older drivers/systems. Some comment on
exactly which setu
From: Artem Galin
Makes selection of d3d11va device type by default and over DirectX 9,
which is still supported but requires explicit selection.
This enables usage of non-powered/headless GPU, better HDR support.
Pool of resources is allocated as one texture with array of slices.
Added d3d11va
