> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of > Artem Galin > Sent: Sunday, May 10, 2020 1:19 AM > To: FFmpeg development discussions and patches <ffmpeg- > de...@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH v4 03/11] libavutil/hwcontext_d3d11va: > adding more texture information to the D3D11 hwcontext API > > On Sat, 9 May 2020 at 22:29, Soft Works <softwo...@hotmail.com> wrote: >
> > You replied: > > > yes, it is only a hint for D11 when possible. > > > > I would understand 'when possible' in a way that D3D9 would be used > > 'when not possible'. > > > > If that's true, it means, that an ffmpeg user executing a command line > > cannot be sure whether D3D9 or DX11 will be used. That would mean that > > the behavior is not deterministic. > > > This is not true, it is your assumptions. > Behavior is deterministic: > DX11 by default. > DX9 if user selects it explicitly via command line. > > > > But still, even with your patch: What will happen when DX11 is not > > > > available? > > > > > > > > Will it > > > > > > > Please read the patch > > > > > 1. fail? > > > Yes Thanks for confirming this. Deterministic behavior instead of auto-selection Is important and should not be changed. But on the other side, it needs to be clear to everybody, that this once again adds even more to the list of situations that the patch will break: In this case, it's all Windows versions where DX11 is not available. Best regards, softworkz _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
