Timecode (MTC / LTC)

CueForge 0.99.1 can receive external LTC and MTC into its show timecode clock. Monitoring a signal and allowing that signal to fire cues are separate operations. Receiving timecode does not automatically arm timecode triggers.

Choose the source

• Internal: CueForge runs the timecode clock itself.
• External LTC: receive timecode through a selected audio input and channel.
• External MTC: receive MIDI timecode through the configured MIDI input.

External timecode drives clock position and crossing-based cue triggers. This is not a claim that all playing media continuously chase or resynchronise to the external source.

Set up live LTC

1. Connect the source’s LTC output to a suitable line input on your audio interface. Keep LTC off loudspeaker and headphone monitoring paths.
2. Open Settings → Timecode and select external LTC as the project source.
3. Set the project frame rate to match the generator.
4. In the LTC input controls, select the audio device and input channel and enable capture. Allow microphone/audio-input permission if the operating system requests it.
5. Keep Timecode Triggers off while checking the incoming level, signal, detected rate and lock state.
6. Wait for Locked and compare the received timecode with the source. Check effective timecode separately if an offset is configured.

Device/channel/enabled input bindings belong to this workstation. Source, rate, offset and project policies travel with the show. Recheck the device binding when moving the project to another computer.

Understand status before arming

An open input is not proof of valid LTC. Capture active, audio level, signal present, lock and rate mismatch describe different conditions. Silence or signal loss freezes the external clock. A reliable mismatch must be resolved before trusting timing.

Frame numbering determines nominal FPS; the number of LTC words arriving per second may differ when a source repeats or skips labels. Rate acquisition needs enough valid second rollovers, typically a few seconds. Do not diagnose a faulty source from word cadence alone. Ambiguous 30-family fractional-rate detection remains a validation limitation.

Fire cues deliberately

1. Set a timecode trigger on each intended cue and enable that cue’s trigger.
2. Verify source lock, frame rate, start/offset and policies with firing disabled.
3. Enable Timecode Triggers only when ready to test the intended cue crossings.
4. Run from before the first target and confirm that each cue fires once as configured.
5. Test stop, loss and reacquisition before using the setup in a show.

STOP, PANIC, disarm and application restart require deliberate rearming. Initial lock or reacquisition establishes a new baseline; it does not replay a backlog of missed cues. Test jumps and your configured crossing policy in rehearsal.

MTC and output

MTC uses the existing MIDI receiver and the same authoritative timecode/trigger path. Match source and project rates, inspect receiver status, and keep cue firing disabled until reception is stable. MTC physical-device acceptance remains specific to your setup.

Timecode input and timecode output are separate features. Receiving LTC does not enable an LTC or MTC output. Rehearse any output configuration separately and never route an LTC test signal to audience speakers.

Verified beta setup and limits

A physical grandMA3 → Studio 1824c Input 8, 48 kHz → CueForge, 25 fps run was checked. With timecode triggers off, no test cues fired. With firing deliberately enabled, four cues fired once at 5, 10, 15 and 20 seconds. This does not certify every generator, rate, interface or platform.

Windows installers are built, but native Windows installation and hardware acceptance remain pending. See Current Limitations and Troubleshooting.