Manual

Triggers

Beyond pressing GO, cues can fire automatically. Configure triggers in a cue's Trigger tab.

#Continue mode (Continue column)

The most common trigger:

• GO — manual GO press is required.
• Auto-follow — fires when the previous cue finishes playing.
• Auto-continue — fires N seconds after the previous cue starts (set post-wait).

#Pre-wait and post-wait

• Pre-wait — a delay between being triggered and actually starting.
• Post-wait — how long to wait before the auto-follow or auto-continue fires.

#Keyboard hotkey

Assign any letter (A–Z) or function key (F1–F12) to a cue. Pressing that key fires the cue directly from the main window. Keys have no effect while a text field is focused.

#Timecode (MTC chase)

Enable "Timecode trigger" and set an HH:MM:SS:FF value. When CueForge2 is chasing incoming MTC, the cue fires as that timecode is crossed.

#Time of day

Enable "Time of day trigger" and set an HH:MM:SS wall-clock time. The cue fires once each day when the clock reaches that time (while the show is open). Useful for installations, exhibitions, and scheduled automation.

#DMX input (Control tab)

Set a DMX trigger channel and level. When the specified incoming DMX channel exceeds that level, the cue fires.

#MIDI input

Bind a cue to a specific Note On, CC, Program Change, or MSC command in Show Settings (global bindings) or in the cue's Control tab.

#OSC input

Send OSC commands to CueForge2's built-in server to trigger any cue.