Programming cues and exporting to lighting consoles

For theater, concerts, film/TV shoots, and worship services that follow a programmed cue stack, the Lighting module's cue list is where the show comes to life. Build cues with fade times, link conditions, and command notes; export to the lighting console the operator runs the show from.

The cue model:

- **Cue number** — usually decimal (1, 1.5, 2, 2.5, 3) so you can insert without renumbering.
- **Label** — short text the SM reads when calling the show ("Lights up Act I," "Storm flash," "Curtain call bows").
- **Channels / submasters / palettes** — what changes in this cue. Pulled from the show's rig (channel = a fixture, palette = a saved look like "Warm Wash" or "Backlight Special").
- **Fade time** — seconds. Up-fade and down-fade can be different ("Up 3, Down 6" for a typical theatrical fade).
- **Delay** — wait time before fade starts.
- **Follow / link** — auto-trigger conditions ("Follow cue 12 after 4 seconds" or "Linked to cue 25.5 — both fire together"). Useful for sequenced looks like chaser effects or a sequence of stings.
- **Note** — for the operator. "GO on 'enter the king,'" "watch for late actor — hold," etc.

Building a cue list:

1. **Open Cues tab** in the show. "+ New cue."
2. **Set a starting look** — the rig's blackout state by default. Or "Inherit from cue X" to start where another cue left off.
3. **Edit the look** — click channels / palettes; set levels. Or import a saved palette from your library.
4. **Set timing** — up/down fade, delay, follow/link.
5. **Add a note** — for the operator.
6. **Save + advance** — cue is in the list. Repeat for the next cue.

Cue list paperwork:

The paperwork generator (see "Paperwork formats" article) outputs a printed cue sheet that the SM uses during performance. Format follows the standard theatrical cue sheet: cue number, label, fade time, page reference (script page), command note. One sheet per act, headers/footers on every page.

Console export:

The platform can export your cue list in the format your console eats:

- **ETC EOS Family (Eos / Ion / Element)** — exports as a CSV showlist + palettes file. Console operator imports via the EOS file browser. All fade times and follow conditions translate cleanly.
- **MA Lighting (grandMA2 / grandMA3)** — exports as XML showfile fragment. Programmer merges into the master showfile.
- **Avolites Diamond / Quartz / Tiger Touch** — exports as a personality-mapped show. Coming Q4 2026.
- **High End Hog 4** — exports as Hog show fragment. In development.
- **CSV (generic)** — for any console that accepts CSV cue import. Columns: cue#, label, channels, levels, up time, down time, delay, follow, note.

Live-driving a console (coming soon):

The next-phase development is driving the console directly from the platform via Art-Net, sACN, or OSC out. Once shipped, a single "Run show" button replaces the export-import-program-program loop. Until then, the export is the bridge.

Programming-day workflow:

1. **Designer builds cues** in the platform — labels, fade times, draft levels.
2. **Export to console** before tech rehearsal.
3. **Programmer + designer refine on the console** during tech. The console becomes the source of truth for the run.
4. **Re-import to platform** (CSV round-trip) — captures final cue list for the show's archive and for post-show paperwork.

Multi-cast / weekly worship workflow:

For weekly services or repeating shows: the cue list is saved as a "Show template." Each week's actual service inherits from the template. Edits flow from template → live show; the SM marks the week's specific changes (sermon length, song additions) inline.