LTCast LTCast
/ Timecode In
Manual › Timecode In

Timecode In

Settings → Timecode In has two sub-tabs: Chase and TC Bridge. Chase makes LTCast follow an external timecode source. TC Bridge forwards incoming timecode to LTCast's MTC, Art-Net and OSC outputs. Chase is free. TC Bridge sends timecode out, so it is a Pro feature: without Pro (an active trial counts) its controls are dimmed and an Upgrade link appears at the top of its tab.

The audio input that carries the external LTC is chosen in Settings → Devices → LTC Input Device, not here. When none is chosen, an amber link at the top of the tab takes you to Devices. You do not need it if chase follows only Art-Net, MTC or OSC.

Chase sub-tab

Chase makes the timecode display, playhead, setlist song and cues follow the external clock; it does not re-broadcast that clock. See Chasing external LTC for how it works. The controls:

  • Enable chase mode — the master switch. The CHASE pill in the status bar and Ctrl+Shift+C do the same.
  • Output audio while chasing — plays the matched song's audio in step with the external clock. Off by default (🔇 MIDI only in the status bar), so you get the display and the cues but no music.
  • Fade out when timecode leaves the song — with chase audio on, when timecode jumps to a time no song covers, the audio fades out over this long after holding for about 0.3 seconds. 0.5 seconds by default, up to 2; 0 stops it right away. A song that simply plays to its end is not affected: its tail rings out. The timecode LTCast sends keeps running until the audio stops, so set this to 0 if what is downstream must stop as soon as possible.
  • After the signal stops: what chase does when the timecode stops coming, whichever input it is following. Stop is the default. Keep going runs on for the seconds in the box beside it (1 to 120, 10 until you change it), then stops. To end of song runs on to the end of this song. Keep going always runs on past the end. A note under the row says what the chosen one does. See Freewheel mode.
    • Wait before calling it lost: a slider from 0.3 to 2 seconds, 0.5 until you change it. A silence shorter than this counts as a late frame.
    • While it keeps going: shown only with Keep going. The box Send triggers (only during those seconds) is ticked until you change it, so a loose cable does not swallow a cue. If the master really stopped, those triggers will have gone out though it never got there. The other choices send no triggers.
  • Art-Net Network Input — also follows Art-Net timecode arriving on UDP port 6454, for example from another LTCast. See Chase from Art-Net.
  • Timecode sources — one row per input (LTC, MTC, Art-Net, OSC), in order: the first is the Primary and the others are Backup. If the input in charge goes quiet for a quarter of a second, the next one still being heard takes over, and the Primary takes back over when it returns. Each row is tagged Following, Standby or Off, has up / down to change the order, and has its own Offset, −99 to +99 frames; positive is later. Chase follows an LTC input about 4 frames late (measured on a Mac at 25 fps; Windows has not been measured) and the LTC offset starts at 0, so to line chase up, set the LTC row to about +4 and measure it with your own audio interface. See LTC input delay.
  • Status — shows Idle, Chasing, Freewheeling or Lost. Lost covers both kinds of stop; the CHASE pill tells them apart as NO SIGNAL and MASTER STOPPED.
  • Entering a song midway: the triggers before it — what chase does with the triggers it passed when it joins a song partway: Don't re-send (default), Re-send the last N seconds, Re-send the last one per destination or Re-send all of them. Saved with the show. See Entering a song midway.

MTC input

The MTC row of Timecode sources has a menu of MIDI inputs. It is Off until you pick a port. If the port is unplugged, the row reads MIDI port not connected and is tagged Off until it comes back. LTCast remembers the port by name as well as by its system ID, so it finds the port again if the system gives it a different ID. Listening does not disturb MIDI remote mappings on the same port.

Quarter-frame messages are a running clock that chase follows. A full-frame SysEx message or MMC LOCATE is only a position, which a stopped master sends when its cursor moves. Chase moves there (the song changes if needed, and the playhead and big timecode move), fires nothing, not even a trigger on that frame, and does not start running, whatever After the signal stops is set to. The CHASE pill reads MASTER STOPPED and the status reads Lost, or it stays on Idle if it has never heard that master running. So a master that sends only full-frame messages never fires a trigger. MMC STOP and MMC PAUSE stop chase at once, with the same pill. TC Bridge does not forward the MTC input yet. See MTC as a timecode input.

OSC input

This input takes timecode and no commands: it has no play, stop or go-to-song message. But the timecode drives chase like any other input, and chase fires the show's triggers as the time passes them, so whoever can send here can set your triggers off. The OSC row of Timecode sources has:

  • Listen: off by default. If the port cannot be opened, LTCast says so and unticks it.
  • A UDP port, 1024 to 65535 (9100 until you change it).
  • From the network: off by default, so only this computer can send here. Tick it and any device on the network can, and the timecode it sends can fire your triggers.

Only messages to /timecode are read, as five integers (hours, minutes, seconds, frames, frames per second), a text string and a float frame rate, or a text string alone. The Generic (/timecode) template of another LTCast's OSC output works. TC Bridge does not forward the OSC input yet. See OSC as a timecode input.

TC Bridge sub-tab

TC Bridge sends each incoming timecode frame on to the outputs you choose, as it arrives, whether or not chase is on and without playing any file. See TC Bridge. The controls:

  • Enable TC Bridge mode — the master switch, off by default.
  • Forward to MTC output, Forward to Art-Net output and Forward to OSC /timecode — which outputs receive the bridged timecode. They stay clickable while the bridge is on; they are greyed out only while the master switch is off.

The bridge does not set those outputs up for you. When a forward is ticked but its output is not ready, an amber hint appears beside it — Select an MTC port first, Enable Art-Net output first, Enable OSC output first — and clicking it jumps to the page where you fix it. Two reminders sit at the bottom of the tab: the bridge is muted while a local song is playing, and it simply stops when the incoming signal drops, with no last-value repeat.