Working with other programs

Cuerunner owns the cue list, the sound and the clock. Everything else in the room is already good at its own job, and a cue is how you ask it to do that job now.

Video

Cuerunner does not play the pictures. Another program owns the projection — Resolume, Mitti, vMix, a media server — and the ones that listen for OSC take the roll from an OSC cue: the cue names the host, the port and the address, so the video roll sits in the same list as the sound, in the same order, fired by the same GO. A program that takes MIDI instead is a MIDI cue, and one that speaks show control takes the go, stop, load or reset of a show-control cue — the same message a lighting console would take.

That boundary is deliberate. One program keeps the clock; two programs keeping the clock is how a show drifts.

Lighting

Buttons, phones and tablets

The showfile

.cuerunner is JSON with a stable byte order: the same show saves the same bytes, so it lives in version control beside the show's notes and its plots, and a diff between two saves says which cues moved. What it does not do yet is read another program's session file — an import from QLab or SCS is a wish, not a feature, and this page will say so until it is not.