Timecode
CueForge includes a timecode trigger family that seeks the internal clock to a mapped SMPTE position. Cues with timecode triggers at or after the seeked position fire on subsequent scheduler ticks. External LTC/MTC input and output are planned for a future release.
What it does
Timecode support in CueForge allows you to align cue playback with SMPTE timecode positions. Timecode trigger mappings seek CueForge's internal clock to a mapped position. Cues with timecode triggers at or after the seeked position fire on subsequent scheduler ticks. External timecode sources (LTC/MTC chase) are planned and are not part of this beta.
Why it matters
In productions with pre-recorded music, dance, or tightly timed multimedia, a single shared timeline provides the backbone for synchronisation. CueForge's internal timecode clock keeps every timecode-triggered cue aligned with that timeline, reducing operator workload and improving timing accuracy. Chasing an external timecode master is planned for a later release.
Typical workflows
- Configure timecode trigger on a cue marker
- Enter the target SMPTE position
- Verify cue firing behaviour during rehearsal
Important limitation
Timecode trigger mappings seek the internal clock only. They do not output LTC or MTC to external hardware, and they cannot receive external timecode.
Current limitations
- No LTC/MTC output. Internal clock seek only.
- No external MTC/LTC input. Hardware sync is on the roadmap.