[FFmpeg-devel] [PATCH v4 03/11] libavutil/hwcontext_d3d11va: adding more texture information to the D3D11 hwcontext API
Soft Works
softworkz at hotmail.com
Sat May 9 23:31:53 EEST 2020
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of
> Max Dmitrichenko
> Sent: Saturday, May 9, 2020 10:16 PM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel at ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v4 03/11] libavutil/hwcontext_d3d11va:
> adding more texture information to the D3D11 hwcontext API
>
> On Sat, May 9, 2020 at 8:13 PM Soft Works <softworkz at hotmail.com> wrote:
>
> > > -----Original Message-----
> > > From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of
> > > Hendrik Leppkes
> > > > >
> > > >
> > > > Of course there is a choice. Only support the new stuff. Afterall
> > > > we havent supported it at all for years now, so only supporting it
> > > > on newer drivers isn't the end of the world.
> > > >
> > >
> > > To give an example for consistency:
> > >
> > > d3d11va decoding will only ever decode into array-textures. So when
> > > I use d3d11va decoding, and then try to encode with qsvenc, it still
> > > fails on
> > such
> > > systems, right?
> > > And not only that, it'll fail in mysterious ways.
> > >
> > > When I'm decoding with qsvdec and it produces a list of textures,
> > > and
> > the API
> > > user does not handle them, since its a new feature and a API change,
> > it'll
> > > break mysteriously again.
> >
> > Nothing will break when ffmpeg supports non-array textures, neither
> > expected nor mysteriously.
> >
> >
> it is not matter of this patches list,
> can it be discussed in other patch review thread?
It is very relevant to this patch set, because supporting non-array textures
or not has a big impact on the number of cases that your patch will break.
Making DX11 the default AND not making sure that command lines will
keep working widely (with driver versions as are deployed in the real world
and not just the very latest ones), that are two things that do not
go together very well, IMHO.
Regards,
softworkz
More information about the ffmpeg-devel
mailing list