When your cues don’t fire

Test fire works, the console responds — and then you press play and nothing happens, or one cue lands and the rest of the song is silent. Test fire proves the MESSAGE is right; it says nothing about WHEN the cue is due. Almost every case of "my triggers don’t work" is about the timing, and there are two things to check.

1. 1

   Make sure the song is selected in the setlist. Cues belong to the selected song, so if the transport is playing something that is not the selected row, every cue stays silent — while timecode keeps streaming, which makes the outputs look perfectly healthy.

2. 2

   Check that each cue’s timecode sits inside the song’s own timecode. LTCast now flags the ones that do not: BEFORE SONG means it will fire the instant you press play, together with every other cue like it; AFTER SONG means its moment never arrives.

   
3. 3

   Fix them by writing the cue in the song’s own timecode. If the song starts at 01:00:00:00, a cue fifteen seconds in is 01:00:15:00 — not 00:00:15:00. The ⏲ button next to each cue stamps the current playhead position, which is the quickest way to get it right.

4. 4

   Still stuck? Turn on the SHOW tab from the View menu and watch the Show Log while the song plays. Every cue it sends is printed there as it goes out, with "late by Ns" on any cue that fired after its own moment. If a cue is not in that log, it never left LTCast.