On Thu Jul 4 22:56:45 2024 +0000, Brendan McGrath wrote:
changed this line in [version 2 of the diff](/wine/wine/-/merge_requests/5978/diffs?diff_id=120655&start_sha=128dc290b03fe1bb5e307780f826b46f2dcdac0b#03c4efe3c0041a988fac0ea9eb3a9e8e49f116f3_114_114)
It turns out the issue wasn't related to the padding; I had simply introduced a bug. Namely I hadn't catered for the use-case where we read from the DXGI buffer rather than write. I've fixed that now, and I now seem to get the same results with and without this MR.
I only hit this issue once I started using an isolated video processor transform and passed it DXGI buffers. Prior to that, I was testing with `IMFSourceReader`, which was passing the transform buffers from wg_parser, which appear not to be DXGI buffers.