Please Help!!! Render errors in 17.3 Build 14

I am not sure what is going on, but when I render out a clip, no matter the codec, my clips look like below. Rendered from FX6 footage (mxf). Please help as I have a deliverable due soon. I was on 17.2 and it was also happening, which is why I upgraded.

https://drive.google.com/file/d/1SAJTSD ... sp=sharing
https://drive.google.com/file/d/1hArxEC ... sp=sharing

Thanks in advance!

What camera was used to film the original footage?

What camera was used to film the original footage?

Sony FX6. Container is MXF and the file is XAVC All Intra 4:2:2, 3840X2160 23.976fps.

Things I have tried:
I have tried rendering in a brand new timeline, tried rendering other clips, tried rendering different resolutions, different codecs, tried removing all colour nodes, tried different ways of rendering (native, nvidia, intel sync). Also this is happening on PC as well as Mac.

OK.

Can you share an original clip for testing?

OK.

Can you share an original clip for testing?

I believe he shared a clip in his original post: https://drive.google.com/file/d/1SAJTSD ... 5n0VJ/view

This looks like the same issue which is being reported here: viewtopic.php?f=21&t=147107

hi,

I had the same problem in DVR 17.3 and 17.3.1 , but for me it helped to switch back to 17.2.2.

Been seeing issues like this in the latest versions on an M1 Mac too, here's my findings from another post:

I've been having some similar issues when working with XAVC footage since the update.

After a lot of experimentation I solved the problem by:

Disabling "Decode H.264/H.265 using hardware acceleration" in preferences

AND (and it really does have to be both of these)

Disabling "Use hardware acceleration if available" in the deliver page (should your output codec support it).

This may not be relevant to a Windows based machine, but might be worth a try!

I also found that ProRes (so if this is the same I suspect DNxHR would be the same on Windows) exports did not have the issue with the decoding acceleration off.

I wonder whether there's been some significant changes in the hardware acceleration recently that's causing this?