Manual

MIDI, OSC & Timecode

CueForge2 integrates with MIDI, OSC, and timecode for full show-control compatibility.

#Sending MIDI

• MIDI Send cues send arbitrary MIDI messages: Note On/Off, CC, Program Change, MSC (MIDI Show Control) commands, and raw SysEx.
• Network cues send MIDI notes/CC/PC to external devices over OSC or MIDI.
• Any cue can send a Note, CC, or Program Change as a side effect (Control tab).

#Sending OSC

• Network cues send OSC messages to any address and port.
• Configure the destination in the cue's inspector.

#Sending timecode

• Timecode cues generate LTC (audio) or MTC (MIDI) streams.
• LTC exits the dedicated LTC Timecode output channel in your audio interface.
• MTC goes out the selected MIDI output port.
• Frame rates supported: 23.976, 24, 25, 29.97 DF/NDF, 30.

#Receiving / chasing MIDI

• MIDI input can trigger cues from: Note On, Control Change, Program Change, MSC Go/Stop.
• Configure in Show Settings which MIDI device to listen on.

#OSC input

• CueForge2 has an OSC server. Use it from any controller, app, or web remote.
• Configure the port in Show Settings or the Remote Settings window.

#MTC chase (timecode trigger)

CueForge2 can follow incoming MIDI timecode (MTC) from an external source. Enable "Timecode trigger" on a cue in the Trigger tab and set its HH:MM:SS:FF position. When the incoming timecode passes that point, the cue fires automatically — keeping CueForge2 locked to the external clock.

Full-frame SysEx position messages and F1 quarter-frame messages are both supported.

#Surface mapping

Open Surface Mapping (Window menu) to bind incoming MIDI or OSC messages to CueForge2 actions globally — GO, Stop, PANIC, navigate, adjust master volume, and more — without tying the binding to a specific cue.