Trigger modes

Each cue has a trigger mode that controls when it fires during playback. Choose the mode that matches how tightly the cue needs to track the timecode versus how much live operator control is required.

Auto

The cue fires automatically when the playhead reaches the cue's timecode position. No operator action is needed. This is the default mode and is suitable for cues that are always in sync with the audio — for example, a lighting scene that always changes at the same moment in the song.

Manual GO

When the playhead approaches a Manual GO cue, LTCast enters standby at the configured lead time before the cue position. The operator must press the GO button (or a mapped MIDI footswitch) to fire the cue.

The standby warning appears early enough to give the operator time to prepare. The lead time is set in the Standby (sec) field in the cue editor.

Use Manual GO when exact timing depends on live conditions — for example, a pyro cue that fires on a performer's action rather than a fixed beat, or a reveal that waits for a stage manager's call.

Follow Previous

A Follow Previous cue fires immediately after the preceding cue in the list completes its standby and fires. The timing is based entirely on sequence — this cue has no independent timecode trigger.

Use Follow Previous to chain related cues without setting individual timecodes for each one. For example, a lighting cue followed by a video trigger that should always fire in that order, back to back.

Choosing a mode

As a general guide: use Auto for timecode-locked cues that never vary, Manual GO for cues that need a human decision point, and Follow Previous to group related cues that always travel together.