SetTimeCode

SetTimeCode belongs to Metadata Nodes. Orange Background receives an image and Output passes it with timecode. The manual names the native tool Set Timecode [TCMeta]; website lesson IDs are not .comp serialization.

Timecode is dynamic: its value depends on the frame position and configured offset. The manual relates Hours/Minutes/Seconds/Frames to the composition starting frame. The lessons explicitly set the start to 0 for reproducibility.

The supplied Inspector offers integer bases 24, 25, 30, 48, 50 and 60. A normal frame component uses 0 through FPS−1. The reference entries 24, 25 and 30 are choices of one FPS control, not separate controls.

With composition start 0, FPS 24 and offset 01:00:00:00, frames 0, 24 and 48 correspond to expected labels 01:00:00:00, 01:00:01:00 and 01:00:02:00. These are lesson calculations; inspect the actual table in Resolve.

Changing the counting basis is not a retiming command and does not change project FPS. The second lesson keeps a 24 fps composition while metadata counts at 25: frame 24 is expected to read 00:00:00:24. Compare the image with its input at that same frame.

The shown interface has no 23.976, 29.97, 59.94 or separate Drop Frame choice. Do not automatically interpret 30 as 29.97 DF. Check another Fuse version and the requirements of a specific export separately.

Print to Console prints the diagnostic relationship between timecode and frames. It is useful for checking a second-boundary rollover. Writing metadata does not create an RGB burn-in or by itself establish the saved file timecode.