LTCast LTCast
/ Chasing external LTC
Manual โ€บ Chasing external LTC

Chasing external LTC

Chase mode turns LTCast into a timecode follower. Another device is the master clock; LTCast reads its LTC signal and follows it. The big timecode display shows the external time, the playhead and Next Cue countdowns move with it, the setlist song that matches that time is loaded for you, and the cues and triggers of that song fire as the external clock reaches them. Playing the song's audio in step with the master is optional.

This page is written around LTC, the usual input. Chase can also follow MTC, Art-Net and OSC, and most of what follows applies to them as well.

Chase does not re-broadcast the incoming clock. The master's time is not re-encoded as LTC, and it does not drive MTC, Art-Net or OSC by itself. Those outputs follow the incoming clock in only two cases: through TC Bridge (off by default), or when LTCast plays the song's audio in step with the master (Output audio while chasing) and the local playback sends its usual outputs. To turn one LTC feed into MTC, Art-Net and OSC, use TC Bridge.

How LTCast finds the song

Chase matches the incoming timecode to a setlist song in one of two ways:

  • LTC inside the song's audio file. When you add songs, LTCast scans them in the background (see LTC scan badges) and remembers which stretches of timecode each file contains. A song with scanned LTC always uses it.
  • The song's Start TC and length. A song with no LTC in its file sits where the TC Generator would play it: from its Start TC plus the global and song offsets, for the length of the file. An Empty Song works the same way, with the length you set. So one show file played by the generator on one computer and chased on another lines up. A song with no Start TC set is not guessed at, and chase cannot find it. To give many songs a Start TC at once, see Set start TCs in order on TC Generator & start TC.

While chasing, LTCast looks the incoming time up in those ranges:

  • If it falls inside a song's range, that song becomes the active song and the playhead goes to the matching position. If two songs cover the same timecode, the one higher in the setlist leads for as long as it covers it, and the other takes over when it ends.
  • If it falls outside every range, the active song stays and the playhead and Next Cue panel hold still, although the big timecode display keeps showing the external time. Triggers of the active song whose timecode falls in that stretch still fire on their own frames. After 3 seconds, No song covers this timecode appears under it, with a Check setlist link to Pre-Show Check.

When chase switches on and finds songs by their Start TC, it says how many (Chase finds n song(s) without LTC by their start TC + length.). If one of those songs overlaps another, it names the two and asks you to give each song its own Start TC. With chase on, Pre-Show Check lists the songs chase cannot find (no LTC in the file and no Start TC, or a length it cannot read) and overlapping ones. In the setlist, the colour of a song's start TC shows how chase finds it: violet through its Start TC, the accent colour through LTC, and, while chase is on, amber --:--:--:-- when it cannot. Hover over it for the full range.

Very long songs and AIFF files are an exception to the background scan. A song too long for the normal decoder (about 1 h 33 min at 48 kHz), larger than about 500 MB, or in AIFF format is decoded through ffmpeg when it loads, and the background scan cannot read it. For such a song LTCast takes the LTC from the file when you load it, so chase finds the song from that first load on and the result is saved with the show โ€” but a long song that has never been loaded is found only if it has a Start TC. See Loading audio files.

Enabling chase mode

  1. In Settings โ†’ Devices, choose the LTC Input Device โ€” the audio input that carries the external LTC. It can be a physical audio interface input, a virtual device (VB-CABLE Output, BlackHole) or a system input. Names appear only after the operating system has given microphone permission; click Grant microphone access if prompted. Next to it, choose the channel: Auto-detect (parallel) listens on channels 1โ€“4 and locks onto the first one that carries LTC, or pick CH 1 to CH 4.
  2. Turn chase on with any of these: Settings โ†’ Timecode In โ†’ Chase โ†’ Enable chase mode; the CHASE pill in the status bar; the CHASE button above the timecode display; the Chase button in the Tour's bottom bar; or Ctrl+Shift+C (Cmd+Shift+C on macOS).

The first time you enable chase while audio output is off, a message explains that the audio is muted by default and links to the setting. If no input device is chosen yet, the Chase tab shows an amber link that jumps to Devices.

Chase is free: the Chase tab and its settings work without Pro. Sending the timecode on โ€” TC Bridge, and the MTC, Art-Net and OSC outputs โ€” needs Pro.

Timecode sources

Chase can listen to several timecode inputs at the same time, but it follows one at a time. Settings โ†’ Timecode In โ†’ Chase โ†’ Timecode sources has one row per input, in order. The default order is LTC, MTC, Art-Net, OSC.

  • The first row is the Primary and the others are Backup. The up and down arrows on each row change the order.
  • If the input in charge is silent for a quarter of a second, the next input that is still being heard takes over. When the Primary returns, it is back in charge from its first frame. Each hand-over is written to the Show Log.
  • Frames from an input that is not in charge are dropped: they do not reach chase, the big timecode or TC Bridge.
  • Each row is tagged Following, Standby or Off. Off means the input is not set up: no LTC Input Device is chosen, the MTC row has no connected MIDI port, Art-Net Network Input is not ticked, or Listen is not ticked on the OSC row.
  • The MTC row has a MIDI port menu (see MTC as a timecode input). The OSC row has Listen, a UDP port (9100 until you change it) and From the network (off: only this computer can send to it; see OSC as a timecode input).
  • Each row has its own Offset, from โˆ’99 to +99 frames, applied before chase and the big timecode. A positive value makes the timecode later. TC Bridge forwards the LTC and Art-Net inputs only, with the offset applied.

The order, the offsets and the MTC and OSC settings are remembered on this computer. They are not saved in the show file.

LTC input delay

Chase follows an LTC input about 4 frames behind the master. On a Mac at 25 fps, with the master's LTC sent through a virtual audio cable (BlackHole), the chase position was measured 160โ€“175 ms late. The LTC decoder has to receive a whole frame before it can report it, and the audio input adds its own buffering. Windows has not been measured, and neither have other frame rates.

The triggers chase fires, and anything TC Bridge forwards from that input, come from the same decoded frames, so they are late as well.

LTCast does not correct for this: the LTC input offset is 0 until you change it. To line chase up with the master, go to Settings โ†’ Timecode In โ†’ Chase โ†’ Timecode sources and set the Offset on the LTC row to about +4 frames. In the Mac test above, +4 frames brought the difference to about 0 ms (between โˆ’25 and +9 ms). Measure it once with your own audio interface before you settle on a number, because a physical interface may add a few milliseconds that a virtual cable does not. The offset is counted in frames, so the same delay is a different number of frames at another frame rate.

MTC as a timecode input

Chase can follow MIDI Timecode from a DAW, a console or another LTCast. The input is off until you pick a port: in Timecode sources, choose a MIDI input in the MTC row's menu (Off is the first entry). If that port is later unplugged, the row reads MIDI port not connected and is tagged Off until the port 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. Like the rest of chase, this input works without Pro.

LTCast reads these messages:

  • Quarter-frame messages are a running clock. Chase follows them frame by frame, as it follows LTC, and triggers fire as the time passes them.
  • Full-frame SysEx messages and MMC LOCATE are positions: "the master is here", with no running clock behind them.
  • MMC STOP and MMC PAUSE are the master saying it stopped. Chase stops at once, with no wait and no running on, and the CHASE pill reads MASTER STOPPED. See Freewheel mode.

The frame rate comes from the MTC itself, which can only say 24, 25, 29.97 drop-frame or 30 fps. It has no code for 23.976 or 29.97 non-drop. The row's Offset can make up for a fixed delay from the MIDI driver or USB.

A position from a stopped master

A DAW sends a position when you move its cursor while it is stopped. Chase goes there and waits:

  • The matching song becomes active if it is not already, and the playhead and the big timecode move to the position. A position outside every song leaves the active song where it is.
  • Nothing fires, not even a trigger on that exact frame. Triggers before the position count as passed. When the master then runs from there, the trigger on that frame fires and the ones before it do not.
  • Chase does not start running on its own, whatever After the signal stops is set to, because the master is parked rather than gone.
  • Once Wait before calling it lost has passed since the last running frame (half a second by default), the CHASE pill reads MASTER STOPPED in grey, and the Status line in Settings reads Lost. If the position moved chase to another song, this happens at once, and the song's audio does not start until the master runs. If chase has never heard this master running, it stays on Idle instead.

A master that sends only full-frame messages, such as another LTCast set to Full-frame (legacy), therefore moves the playhead but never fires a trigger and never shows Chasing. Use quarter-frame for following. Chase does not follow a master running backwards either: quarter-frames counting down count as positions in the same way.

TC Bridge does not forward the MTC input yet, so nothing goes out through the bridge while MTC is the input in charge.

OSC as a timecode input

Chase can follow timecode sent as OSC messages, for example from another LTCast or a show controller. 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. It moves the playhead and the song, and chase fires the show's triggers as the time passes them, so whoever can send here can set your triggers off. It works without Pro. The settings are on the OSC row of Timecode sources:

  • Listen is off by default. Tick it to open the port. While it is off the row reads timecode only, no commands.
  • The UDP port is 9100 until you change it, and can be 1024 to 65535. If the port cannot be opened, LTCast says so (for example OSC timecode input: port in use) and unticks Listen.
  • From the network is off by default, so only this computer can send here. Tick it and any device on the network can.

With From the network on and chase on, any device on the network that sends valid /timecode messages to this port can fire your triggers while OSC is the input in charge. That includes OSC taking over as a backup when the inputs above it in the order go quiet. Leave it off unless you need it.

Only messages to the address /timecode are read, in one of three forms:

  • Five integers: hours, minutes, seconds, frames and frames per second. This is what the Generic (/timecode) template of OSC Output sends, so one LTCast can follow another. That template sends a whole number: 29.97 as 30 and 23.976 as 24. A 30 here counts as 29.97, and a 24 as 23.976, when the TC Generator's Frame Rate on this computer is set to that rate.
  • A text string HH:MM:SS:FF and a float frame rate.
  • A text string alone. The frame rate is then the one in the grey chip beside the TIMECODE label above the big timecode.

In a text string, ; before the frames means drop-frame, and a frame rate of 29.97 always counts as drop-frame. The frame rate must be 23.976, 24, 25, 29.97 or 30, and the whole numbers 23 and 29 count as 23.976 and 29.97. Other addresses, other forms and OSC bundles are ignored. LTCast also limits each sender to 200 messages per second, which is far above any timecode stream.

OSC has no separate position message: every message counts as a running frame. A sender that stops sending therefore reads as a dropout, handled by After the signal stops, the same as LTC stopping.

TC Bridge does not forward the OSC input yet, so nothing goes out through the bridge while OSC is the input in charge.

Status indicators

Chase has four states:

  • Idle โ€” chase is on but no running timecode has been heard yet.
  • Chasing โ€” valid timecode is arriving and LTCast is following it. Gaps shorter than Wait before calling it lost (half a second by default) are ignored.
  • Freewheeling โ€” the timecode stopped and After the signal stops says to keep going: the chase clock keeps counting on the computer's own clock.
  • Lost โ€” chase has stopped: the timecode stopped and that setting says to stop or its seconds have run out, or the master said it stopped, or the last thing heard was a position from a stopped master. A stop lasts until running timecode arrives again.

You see the state in several places. The CHASE pill in the status bar and the CHASE button above the timecode display say what is happening: CHASE ยท LTC (or MTC, Art-Net, OSC) with a cyan dot while following that input, FREEWHEEL ยท 7 s with an amber dot while running on, NO SIGNAL with a red dot when the signal is gone, MASTER STOPPED with a grey dot when the master stopped, and plain CHASE while idle. Freewheel mode has the full table. The Chase tab in Settings spells the state out. While chasing, the timecode display carries an EXT badge, and when the signal is gone a flashing red TIMECODE SIGNAL LOST line appears under the digits. The line does not appear for a master that stopped. The setlist header shows a CHASE LOCKED badge.

The setlist while chasing

Once chase has heard LTC (Chasing, Freewheeling or Lost), the external source decides which song is current, so the setlist is locked: a "Chase locked โ€” Disable Chase to switch songs manually" overlay covers it, and clicking a song only shows a message to that effect. The keyboard shortcuts that preselect or start songs (โ†‘, โ†“, Enter) and the arrow-key scrub are ignored too. Changing the song or the show by hand is locked as well. Dropping an audio file or a setlist row onto the window, File โ†’ Load Song and a MIDI remote Go to song are refused with "Chase is running โ€” stop Chase to change the song manually". Opening, importing or starting another show โ€” the File menu, Ctrl+O, the saved-show picker, New show, or a .ltcast file opened from the operating system โ€” is refused with "Chase is running โ€” stop Chase to open or start another show". Turn chase off to pick songs by hand. In the Next Cue panel and the Calling Script, clicking a cue to jump is also disabled while chase owns the playhead.

Cues while chasing

The triggers (MIDI, OSC and Arena) of the active song fire when the external time passes their trigger timecode, with the same one-frame precision as normal playback. If the master jumps or scrubs, LTCast treats it as a seek: triggers before the new position are marked as already fired, a trigger on the landing frame fires, and the ones after it are armed again. A jump back into a song's first second fires its opening triggers again. While the chase clock is freewheeling, triggers go out only under Keep going with its Send triggers (only during those seconds) box ticked; see Freewheel mode for what that costs if the master really stopped. Otherwise none go out, and the ones passed during a dropout of more than a second are not sent when the signal returns. The Show Log counts them.

Entering a song midway

Chase enters a song midway when it picks up a master that is already running, or when the master jumps into a song. By default the triggers before that point are skipped, so nothing goes out in a burst. Entering a song midway: the triggers before it in Settings โ†’ Timecode In โ†’ Chase can re-send some of them:

  • Don't re-send (default): nothing is re-sent.
  • Re-send the last N seconds: the triggers in the N seconds before the entry point. N can be 1 to 3600 and starts at 10.
  • Re-send the last one per destination: for each destination, only the last trigger before the entry point, so each device lands where it should be. A destination is an OSC address; a MIDI channel with its program change, CC number or note; or an MSC device ID. Arena columns count as one destination, and Arena clips count per layer.
  • Re-send all of them: every enabled trigger of the song before the entry point.

Re-sent triggers go out at the entry, in timecode order, before any trigger on the entry frame. The Show Log marks them [chase] [lookback]. When the master jumps forward inside a song, only what it skipped is re-sent. The setting is saved in the show file, and a new show starts with Don't re-send (default).

Two cases do not count as entering midway. A song entered within the first second of its timecode sends every trigger up to that point, whatever the setting. A signal dropout that comes back re-sends nothing.

Audio output while chasing

By default LTCast does not play the song's audio while chasing โ€” you get the display, the playhead and the cues only. The status bar shows ๐Ÿ”‡ MIDI only next to the CHASE pill; click it, or tick Output audio while chasing in Settings โ†’ Timecode In โ†’ Chase, and it changes to ๐Ÿ”Š AUDIO. With audio on:

  • LTCast plays the matched song from the master's current position and re-aligns if the master jumps by more than half a second.
  • When chase moves to another song, the song loads and its audio starts at the master's current position โ€” not at the start of the song's LTC, and not where the master was when the song change was detected. A long song can take a few seconds to load, and the audio still lands where the master is by then.
  • When chase stops (NO SIGNAL or MASTER STOPPED), LTCast pauses the audio so it does not run on unsynchronised. While the clock is freewheeling, the audio keeps playing. See Freewheel mode.
  • A deliberate Pause is respected: chase will not restart audio you paused by hand until you press Play.
  • Triggers still go out from chase alone, once each.

This is useful when the master carries no music and LTCast supplies both sync and playback. The outputs that come from that local playback โ€” the file's LTC, MTC, Art-Net and OSC โ€” behave as in normal playback, including the Pro rule for outputs.