Sander de Regt wrote:Were you by any chance rendering to pngs as an image sequence? These are notoriously slow to write from Fusion. PNGs were never intended to be a container for high end compositing images, writing to a different kind of image sequence might speed up the whole render quite a lot.
Good catch. I was exporting PNGs. They're actually incredibly common in a VFX pipeline. But as I had to bring the image sequence back in to Fusion to export a 444 ProRes file I changed my export to EXR, and it rendered exponentially faster, but of course now my hard drive is bloated with all the superfluous renders.
birdseye wrote:So just to confirm, if you view the Saver node the duplicate frames are not present, if you export to another similar codec ie DNxHR, the duplicate frames are not present and you have tried different video players
Correct(ish). Everything looks perfectly fine through the saver node, and the issue is not present when rendering image sequences (both EXRs and PNGs). I tried two QuickTime codecs (ProRes 4444, and H.264) and in both cases the issue remained. I have not tried an alternate wrapped codec (such as DNxHR), but I could give it a try as it could be QuickTime specific.
birdseye wrote:As a wild guess the TimeStretcher node may be causing an issue depending on how you are using it. If you could post the nodes someone might spot a cause and we all might learn something.
I've had this thought, but rendering without the TimeStretch node (either muted or deleted) did not solve the issue. However, it does seem that new projects created that never had the TimeStretch node do not have this issue. This is quite strange, but still seems to indicate the TimeStretch node is the culprit.
I'm new to both Fusion and this Forum, so how might one go about "Post[ing] the nodes"?
Many thanks,