Trigger types
LTCast supports five trigger types, each targeting a different protocol. Choose the type that matches what your target device expects. You can mix types freely within a single song's trigger list — for example, a Note-on to Resolume at bar 1 and an MSC GO to Eos at bar 9.
Note-on
Sends a MIDI Note On message followed immediately by a Note Off, equivalent to pressing and releasing a piano key. Parameters: Channel (1–16), Note (0–127), Velocity (0–127).
Used by Resolume Arena for clip triggers (note number = column, velocity = layer), some lighting consoles that map notes to cue go commands, and most general-purpose MIDI-enabled software. It is the most broadly compatible trigger type.
CC (Control Change)
Sends a MIDI Control Change message. Parameters: Channel (1–16), CC Number (0–127), Value (0–127).
Used for faders, knobs, and switches — for example, controlling a Resolume effect parameter, adjusting a lighting dimmer channel, or toggling a function on a hardware controller. Unlike Note-on, CC sends a single message with no automatic off; the value stays at whatever you send until the next CC on the same number.
PC (Program Change)
Sends a MIDI Program Change message. Parameters: Channel (1–16), Program (0–127).
Used to switch scenes or presets — loading a new bank of clips in Resolume, switching to a different cue list on a lighting console, or recalling a patch on a synthesizer. Program Change is a single message with no associated value beyond the program number.
MSC (MIDI Show Control)
Sends a SysEx MIDI Show Control GO command. MSC is the standard used by professional lighting consoles including ETC Eos, Strand, and Chamsys for timed cue-go commands. The MSC cue number is derived from the trigger's Label field — label your MSC triggers with the cue number (e.g., 12.5) so LTCast embeds the correct cue reference in the SysEx payload.
MSC uses the trigger label as the cue number. If your label reads "Lights Q12", the MSC cue number sent will include that full string. Check your console's MSC cue-number format and match your labels accordingly.
OSC
Sends a custom OSC (Open Sound Control) message over UDP. Parameters: Address (e.g., /clip/play), Arguments (integers, floats, or strings separated by spaces).
OSC is used by software that does not support MIDI — Resolume Avenue/Arena's extended control surface, disguise (d3), Watchout, Millumin, and others. The OSC trigger uses the IP address and port configured in Settings → Outputs → OSC Output; it does not have its own per-trigger destination.
If your target device supports both MIDI and OSC, prefer MIDI Note-on or CC for triggers — MIDI timing jitter is negligible, and MIDI is universally supported. Use OSC triggers only for devices that require it.