OSC & MIDI control

For setting it up, see firing cues from a console. This is the message-level detail.

What Cuerunner listens on

Input	Default	Notes
OSC	UDP port 53000	Every message is published to the Monitor and the run log with its sender and arguments.
MIDI	the ports you tick	With none ticked, every input is opened. An interface that disappears mid-show is reported, because a cue sending down it would otherwise play nowhere in silence.

Panic from anywhere

Two messages stop the show whoever sends them, with no cue written for them:

Message	Effect
`/cuerunner/panic` (any arguments)	Panic: everything stops with a 200 ms fade.
MIDI All Sound Off — controller 120, value 0, any channel, any listened port	The same.

Both are acted on where the engine is rather than in the window, so the fade starts whether or not the interface is answering. The run log records the sender: [main] panic (osc): /cuerunner/panic from 192.168.1.24:8000.

What a trigger matches

Kind	Matched on	Ignored
OSC	The address, exactly.	Arguments.
MIDI note	Port, channel and note number.	Velocity — a note fires whatever it was played at.
MIDI control change	Port, channel and controller number.	Value.
MIDI program change	Port, channel and program number.	—
Show control	Every field the console sent: command, format, device ID, and the cue and list where they are carried.	—

A trigger fires its cue exactly as GO would, pre-wait and advance included. A disarmed cue ignores its triggers. The repeat guard (Settings → General) applies to triggers as well as to the space bar.

What Cuerunner sends

Cue	What goes out
OSC cue	The address and its typed arguments, to the host and port on the cue.
MIDI cue	Its list of messages, on the cue's port or the show's default output.
Show Control cue	An MSC message: command, equipment format, device ID (127 reaches everything), and cue and list where the command carries them.
Scene cuePro	The scene's membership first — which channels it places on which faders, and the faders it takes them off — then each mic's mute, for the channels a recall moves and no others. Nothing outside the show's own channels is named: a mute carries the channel's own number, never a fader's, and a channel the scene leaves off every fader is closed. A mic that changes fader is never muted by the move: it keeps playing and takes the new fader's position. The membership goes over the desk's own route — an SQ's control service on TCP 51326, an Avantis's NRPN `40` on the desk link — and a desk with no membership route reports the gap while the mutes go anyway.

The desk a scene cue drives is set up once in Show Settings → Channels, where the read-back line says which of the show's channels a recall will touch and what the desk it names can be told. What goes out is the difference against what Cuerunner last sent, held for the session and never undone, and each write is remembered as it lands: there is no read-back of a recall's own writes, so a fader moved by hand at the desk is invisible here: recalling a scene again sends only what has changed since the last send, and that record lives for as long as the show is open. Reopening the show forgets it, and the next recall writes every channel the scene controls.