> -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of > Artem Galin > Sent: Tuesday, March 10, 2020 5:10 PM > To: FFmpeg development discussions and patches <ffmpeg- > de...@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH v2] lavc/qsv: adding DX11 support > > Any comments on updated patch by link below: > https://patchwork.ffmpeg.org/project/ffmpeg/patch/20200306130954.8938- > 1-artem.ga...@gmail.com/
I don't see any comments there. [...] > > >> > > > Could you help me to reproduce this unusual behavior where texture > > > need > > not > > > be the same for all frames in a frames context? > > > > It's the default behaviour of a D3D11 frames context; it only makes a > > single array texture when you set a fixed size at the start > > (specifically for the decode use-case which requires a single array > > texture). So for example d3d11 + hwupload filter will do this. The D3D11 hardware context needs to be extended to support non-array texture-pools. Otherwise a significant range of graphics devices would fail to work (practically all that don’t have drivers supporting the most recent SDK versions. 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".
