Timecode
Overview
Grid Studio supports working with external and internal timecode sources to synchronize systems, timelines, and automated processes.
To use timecode within a project, a Timecode Provider is required. A Timecode Provider is responsible for generating or receiving a timecode signal that can be used throughout the system.
Timecode Providers are typically created as objects in the Project Tree, such as:
LTC
MIDI Timecode (MTC)
Embedded SDI Timecode
In addition to these external sources, Grid Studio also provides internal time sources that can be used without creating a project object:
System Time
Local Time
These sources can be used for basic synchronization or scheduling tasks.
Timecode Manager
Grid Studio includes a Timecode Manager that allows defining global timecode providers used by different parts of the system.
Up to four global timecode roles can be configured:
Main
IO
Timeline
Recording
Each of these roles can reference a specific timecode provider.
Opening the Timecode Manager
The Timecode Manager can be accessed from the System Status Bar.
To open it:
Locate the TC indicator in the Status Bar (next to the Project FPS display).
Click on TC.
This will open the Timecode Manager inside the Inspector, where global timecode providers can be configured.
Main Timecode
The Main Timecode is used as the primary system time reference.
When defined, this timecode will also be displayed in the System Status Bar in the top-right corner of the interface.
This allows users to monitor the active system timecode while working in the editor.
IO Timecode
The IO Timecode provider is used when embedding timecode into outgoing protocols that support timecode transmission.
Protocols that support embedded timecode will automatically use the provider assigned in this field.
Recording Timecode
The Recording Timecode provider is used when recording data through Timeline recording features.
The selected provider defines the time reference used for timestamps during recording.
Timeline Timecode
Timelines can also use timecode providers for synchronization.
When a timeline is created, it can act as a timecode provider itself. This allows timelines to drive other systems or workflows using their internal time.
Alternatively, a timeline can be synchronized to an external timecode provider.
Timeline Synchronization
Each timeline allows selecting a Timecode Provider for synchronization.
This allows the timeline to follow an external time source.
An offset can also be configured.
Because timelines always start at 0, the offset can be used when synchronizing to timecodes that begin at a different time.
Example:
External timecode starts at:
The timeline itself still starts at:
By defining an offset of +2 hours, the timeline can be aligned with the external timecode without modifying the timeline content.
Using Timecode in Workflows
Workflows can react to timecode events using the Timecode Event.
This event allows triggering an action when a specific timecode value is reached.
To configure a Timecode Event:
Add a Timecode Event to the workflow.
Select the desired Timecode Provider.
Define the timecode value that should trigger the event.
Unlike continuous listeners, this event only triggers once when the defined time is reached, similar to a button press or scheduled action.
Using Timecode in Modifiers
Modifiers provide a Timecode Node that outputs the current timecode value continuously.
Unlike workflow events, which trigger only once, the modifier timecode node updates every frame.
This makes it useful for:
time-driven animations
parameter modulation
timeline-based calculations
The node also allows selecting the desired Timecode Provider.
Timecode Provider Settings
External timecode providers (such as LTC or MTC objects) provide additional configuration options inside their object settings.
These settings allow adjusting how incoming timecode is interpreted and processed.
Offset
An offset can be applied to the entire provider.
This allows shifting the incoming timecode forward or backward without modifying the original source.
Interpolation
Incoming timecode is interpolated to match the project frame rate.
Several interpolation modes are available:
Adaptive Interpolation
Provides sub-frame precision and allows very accurate synchronization.
However, this can result in a frame being updated multiple times if the incoming signal fluctuates.
None
No interpolation is applied.
The system will use the incoming timecode values directly.
Full Frame Interpolation
Ensures that updates occur only on full frame boundaries.
This mode avoids multiple frame updates and can produce more stable behavior in certain workflows.
Drop Behaviour
Defines how the system behaves if the timecode signal is lost.
Stop
The provider stops advancing when no timecode is received.
Continue
The provider continues advancing internally until the external signal returns.
Once the external signal is available again, the system re-synchronizes automatically.
Timecode Analysis Tools
Grid Studio provides two analysis tools for diagnosing timecode behavior.
These tools help evaluate signal timing and synchronization quality.
Opening Timecode Analysis Tools
To open the analyze tools:
Select the Timecode Provider object in the Project Tree.
Open the Timecode tab in the Inspector.
In the top-right corner, two icons are displayed.
Clicking either icon opens the corresponding floating analysis window, allowing the signal behavior to be monitored in real time.
Quality Analyzer
The Quality Analyzer visualizes the stability of the incoming timecode signal.
The analyzer displays a graph representing the timing stability of the timecode in milliseconds. The goal is to achieve a perfectly straight line, which indicates a stable and consistent timecode signal.
If the incoming signal contains jitter or irregular timing, the graph will show visible deviations from a straight line.
The graph can display multiple lines simultaneously, allowing users to compare the original signal with the internally processed or interpolated timecode.
This makes it possible to clearly observe how interpolation methods affect the incoming signal and how effectively they smooth or stabilize the timecode.
The Quality Analyzer is particularly useful when:
diagnosing unstable timecode signals
evaluating signal jitter
analyzing interpolation behavior
verifying synchronization quality from external devices
Timing Analyzer
The timing analyzer shows when the timecode signal arrives within a frame.
This helps determine how well the incoming signal aligns with the internal frame timing.
Last updated