Freewheel mode
When the timecode that chase is following stops coming, LTCast cannot tell a loose cable from a master that really stopped. After the signal stops is your rule for that moment. Running on the computer's own clock with no timecode coming in is called freewheeling, and the CHASE pill reads FREEWHEEL while it happens.
The setting is in Settings → Timecode In → Chase. It is one rule for this computer, whichever input chase is following, and it is not saved in the show file.
It replaces the two checkboxes Keep running when LTC stops and Run past the end of the song, and your old choice carries over: off is now Stop, on is To end of song, and on with the second box ticked is Keep going always.
The four choices
- Stop is the default. Chase stops where it is and audio pauses.
- Keep going runs on for the number of seconds you type in the box beside it, from 1 to 120 (10 until you change it), then stops the same way. It is the only choice that can send triggers. If the song ends first, the clock waits at the end of the song until the seconds are up.
- To end of song runs on to the end of this song and sends no triggers. If the file has several LTC segments, that means the end of the current segment. The clock then waits there, still freewheeling, until timecode comes back or you switch chase off.
- Keep going always runs on past the end of the song, with no limit, and sends no triggers. It stays on the same song, because only incoming timecode can change the song.
A note under these controls repeats what the chosen one does.
What keeps going
Running on keeps only the chase clock going: the playhead, the Next Cue countdowns and the song time left. Audio that is already playing keeps playing. The big timecode digits come from incoming frames, so they hold at the last frame, unless Output audio while chasing is on and they follow the local playback. Running on does not generate MTC, Art-Net or OSC. Outputs that were being forwarded by TC Bridge stop when the timecode stops. Downstream devices stay fed only if LTCast is also playing the song's audio locally (Output audio while chasing), because that local playback sends its own outputs.
Wait before calling it lost
A slider from 0.3 to 2 seconds, in steps of 0.1, set to 0.5 until you change it. A silence shorter than this counts as a late frame: chase stays on Chasing and nothing changes. The choice above takes effect when the wait is over, and the seconds of Keep going count from there.
The shortest wait is still longer than the quarter of a second a backup input takes. If a second input is running under Timecode sources, it takes over before chase reports a dropout. See Chasing external LTC.
Sending triggers while it keeps going
With Keep going chosen, a third row appears, While it keeps going, with the box Send triggers (only during those seconds). It is ticked until you change it. Each trigger the clock reaches then goes out once, so a loose cable does not swallow a cue. These triggers run from a check every 100 ms rather than from incoming frames, so one can go out up to a tenth of a second late, and one that came due during the wait goes out as soon as the wait ends.
The price. If the master really stopped, the triggers in those seconds will have gone out though it never got there. Lights or video can fire for a moment in the show that has not happened. When the master later runs on from where it stopped, the triggers already sent do not go out a second time. If a wrong trigger would be worse than a missed one, untick the box or use another choice.
With the box unticked, or with any other choice, no trigger goes out while the clock runs on. What happens to the ones it passes depends on where the timecode comes back:
- Within a second of where it was, the frames count as one continuous run, and those triggers go out when the signal returns.
- More than a second further on, those triggers are not sent. If the master simply ran on during the silence, a line in the Show Log counts them: Chase: n triggers were passed during the dropout and not sent.
What the status pill says
The CHASE pill in the status bar and the CHASE button above the timecode display show the same text:
| What is happening | The pill reads | Dot in the status bar | Status in Settings |
|---|---|---|---|
| Chase is on, no running timecode heard yet | CHASE | Grey | Idle |
| Following an input | CHASE · LTC (or MTC, Art-Net, OSC) | Cyan | Chasing |
| Running on under Keep going | FREEWHEEL · 7 s: the seconds left | Amber | Freewheeling |
| Running on under To end of song | FREEWHEEL · 42 s: the time left to the end of the song | Amber | Freewheeling |
| Running on under Keep going always | FREEWHEEL | Amber | Freewheeling |
| Stopped because the signal is gone | NO SIGNAL | Red | Lost |
| Stopped because the master said so | MASTER STOPPED | Grey | Lost |
NO SIGNAL also shows a flashing red TIMECODE SIGNAL LOST line under the big timecode digits. MASTER STOPPED does not, because a master that stopped is not an alarm. In the health strip, freewheeling counts as needing attention and both kinds of stop count as a failure. The viewer page and LTCast as Viewer show only FREEWHEEL or LOST, without the seconds or the reason.
The Show Log keeps a line for each change: Chase: timecode stopped, keeping going on the internal clock, Chase: timecode is back, Chase: no signal, stopped and Chase: the master stopped.
When the master says it stopped
On the MTC input, MMC STOP or MMC PAUSE from the input in charge stops chase at once, with no wait and no running on, whichever choice is set. The same pill appears after the wait when the last thing heard was only a position (a full-frame message or MMC LOCATE), because a master that is parked has not dropped out. A position that moves chase to another song stops it at once: the song loads, and its audio does not start until running timecode arrives.
How long a stop lasts
A stop lasts until running timecode arrives again, however long that takes. Changing After the signal stops does not restart it. A position message moves the playhead but does not restart it either. Switching chase off ends it, and chase then starts again from Idle when you switch it back on.
When the timecode returns
On the first running frame the status goes back to Chasing. If Output audio while chasing is on and audio was paused by the stop, it plays from the master's position, unless you paused it by hand. If the signal returns at a different position than the chase clock reached, the display and playhead jump to it, and local audio (if on) re-aligns.
Running on is most valuable for brief, unexpected dropouts such as cable bumps, a loosening connector or short interference. For longer outages the clock will drift from the true timecode, because it relies on this computer's clock rather than the master's. Re-locking when the signal returns is then the correct behavior, and the jump on re-lock is expected.
System clocks are accurate to a few milliseconds per minute but are not SMPTE-grade oscillators. For shows where sub-frame accuracy matters after a dropout, protecting the cable run is better than relying on freewheel.