Set Fusion Timecode
Retain Source Timecode in DaVinci Resolve 21's Fusion Page
If you are using DaVinci Resolve 21, you might have noticed that the Fusion page is currently unable to view the source timecode coming from the edit page. Retaining source timecode in your renders is incredibly useful, especially since Saver nodes in version 21 have excellent new metadata variables. Keeping this metadata allows you to perform a conform with matching timecode, ensuring your workflow remains precise. Fortunately, there is a straightforward workaround using the Set Time Code node and a little bit of frame offset math . Here is a step-by-step guide to keeping your workflow entirely within Fusion without losing your vital timecode data.
The Problem: Missing Timecode in Fusion
When you look at the metadata of a clip in the Fusion page (by hitting V to open the sub-view menu), you will see a long list of good information, but the timecode is noticeably absent . Because Fusion operates based on frame counting (starting at frame zero), we cannot simply enter the timecode exactly as it appears . Instead, we have to manually calculate and inject the proper timecode offset.
The Core Solution: Frame Offset from 0
The entire magic of this workaround relies on a simple mathematical formula . If you only remember one thing from this guide, it should be this calculation:
Start with your composition's start frame. I use 997.
Subtract 997 (or your specific project start frame offset). If your start frame was 1001, just subtract 1001
Add the frame value of the timecode you copied from the edit page.
It should look like (-997) + (copied frame value from edit page)
Note: The 997 start frame is a project-level setting introduced in recent DaVinci Resolve versions, often used to account for things like four-frame handles. If your start frame is zero and you never use handles (which rarely happens in the real world), you won't need this offset and can leave the frame values alone.
Match Frame and Copy the Source Timecode
Go to the Edit page and place your playhead at the very first frame of your composition (you can use the up arrow key to jump there).
Press F on your keyboard to execute a "Match Frame".
In the top right corner of your source monitor, right-click the source timecode and select Copy Timecode.
Add the Set Timecode Node
Open the Fusion page.
Right before your Saver node (or right at the top of your comp after your media in), drop in a Set Timecode node . (You can easily find this by hitting spacebar and typing "set time code".)
Enter the Values and the Expression
In the Set Timecode node's inspector, paste or manually punch in the timecode you just copied (e.g., 19:18:12:20).
Make sure your frame rate settings match up (for example, choosing 23.98 or 24 frames per second).
Instead of leaving the final frame value as an explicit static number, right-click the word "Frames" in the inspector to create a simple math expression .
Type your offset calculation in parentheses. For example: -(997) + 20 (where 20 is your copied frame value).
Hitting return will generate a negative frame number in this field, but it will successfully output the correct timecode value to your Saver node.
Spot Check and Render
If you want to verify the frame values being injected, go to Workspace > Console.
Spot check a few frames to ensure the console output matches the Edit page timecode.
Once everything matches, render your composition using the Saver node (using the shortcut Command/Control + Shift + R). This is a custom hotkey I setup in last weeks tutorial on the saver metadata variables.
When you import the rendered EXR sequence folder back into the Media Pool as a media asset, switch to list view—you will see it now carries the correct start timecode instead of defaulting to zero.
Why Stay in Fusion?
You might be wondering: Can't I just render individual clips from the Deliver page and keep the timecode that way? Yes, of course, you can . However, working directly in Fusion and utilizing a Saver node is incredibly beneficial for speeding up your workflow . It prevents you from breaking your "Fusion mindset" and keeps your compositing process streamlined in one place .
