On Mon Jul 1 07:15:45 2024 +0000, Nikolay Sivov wrote:
Have you checked if this attribute applies to d3d11 device manager as well, and not only for d3d9?
The tests (`test_topology_loader_d3d11`) cover that? There's one difference between d3d9 and d3d11 with how `MFTOPOLOGY_DXVA_FULL` / `MFT_OUTPUT_STREAM_CAN_PROVIDE_SAMPLES` are behaving: d3d11 inserts a copier in case a transform *can* allocate sample without a device manager while d3d9 doesn't. I chose to follow d3d9 behavior here, and avoid an unnecessary copier.
I don't think we have that behavior anywhere anyway, MFT_OUTPUT_STREAM_CAN_PROVIDE_SAMPLES isn't used in our transforms, and not necessarily a sign that the transform will allocate its own samples, but native probably takes the safest path.