To fix a DaVinci Resolve render failing on a Fusion clip, you can disable “Stop renders when a frame or clip cannot be processed” in the User preferences.
Alternatively, you can “Render in Place” the Fusion composition or delete and re-add the Fusion clip. If the issue persists, disable problematic effects within the Fusion tab, clear the render cache, or try rendering at a slower frame rate.
Quick Solutions
- Disable Error Stop:
Go to DaVinci Resolve > Preferences > User > UI Settings and uncheck “Stop renders when a frame or clip cannot be processed”. This will skip over the problematic frame, allowing the render to complete, though it might result in a glitch or “media offline” warning at that point.
- Render in Place:
Right-click the problematic Fusion clip on the timeline and select “Render in Place” to pre-render it as a new media file, offloading the work from the delivery process.
Troubleshooting Steps
Identify the Problematic Clip:
If you leave the “Stop renders” option checked, Resolve will stop at the exact frame where the error occurs. This gives you a clue to the problematic Fusion clip.
Delete and Re-Add:
Delete the clip from the timeline or the render queue, then add it back and try rendering again.
Clear Render Cache:
Go to Playback > Delete Render Cache > Delete All to clear any corrupted cached data that might be causing issues.
Adjust Fusion Effects:
Open the Fusion clip, disable potentially problematic nodes or effects, or disable keyframe stretchers if they are causing issues.
Slow Down Render Speed:
In the render settings, try a lower render speed (e.g., 50 fps) to reduce the strain on your computer and prevent it from overtaxing during the render process.
Advanced Options
Check System Specs:
Ensure your hardware (CPU, GPU, RAM) and GPU drivers are sufficient for the complex Fusion effects you are using.
Render in Isolation:
If all else fails, you can try to isolate the Fusion composition and render it as a separate file before bringing it back into your main project.
All of the above, were, fixes sent to me when I had a similar issue. The first one and render in place sorted mine out.