- Posts: 1111
- Joined: Wed Aug 22, 2012 10:31 am
- Location: Tallinn, Estonia
It happens to us occasionally, and has for a long time. I’ve been fighting the bug for years. I think it has something to do with how Resolve reads the XAVC-I footage.
I’ve seen it happen on an NVIDIA 9-series TITAN X on a MacPro5,1, dual AMD FirePros on a MacPro6,1, as well as a NVIDIA 1080 Tis on HP Z8s running either Windows or Linux.
Usually on the Z8s, if we’re still just scrubbing through the Color page, grabbing the playhead and scrubbing back over the problem area, forcing Resolve to read the file from disk again, we can get the correct frame.
However, if you’re running into the problem during renders, my bulletproof workaround is to just cache the source [now “Fusion page output” in 15] to a good DI format. On a Mac, use ProRes 4444, or on Windows or Linux, use DNxHR RGB 444, and check the option to used those render cached images on the Deliver page.
Sent from my iPhone using Tapatalk