Venue & AV.

You make rooms light up on schedule. This mission takes Luxaudica from "app on a Mac" to "node in the rig" — mapped into the desk over OSC, running its own show clock, safe under pressure.

The mission

1. Walk the signal path first

   Press c — the connections canvas draws every input and output as a live map with pulsing wires. Confirm audio in, displays out, and any OSC/MIDI sources are present before you build anything.

   why: five seconds of map beats an hour of "why is it not reacting".

2. Outputs & color

   Fullscreen the output on the projector/LED processor. The app auto-negotiates the deepest color the chain supports (10-bit wide gamut where available) with anti-banding dither.

   why: big soft gradients on a 6-meter wall are where 8-bit banding goes to be seen. The app handles it — you just confirm.

3. Pick Festival tier — if the Mac earns it

   Quality tier Festival adds resolution and shadow detail. Watch the perf readout for 5 minutes of busy content; any throttling → back to Tour.

   why: the perf readout is honest by design. Believe it over your optimism.

4. Wire the booth via OSC

   Enable OSC control in Settings → Network, then copy the addresses you need from the OSC reference into the desk — every parameter, scene, look, cue, blackout and panic has one. A desk that speaks OSCQuery finds the whole map itself — the app advertises it on Bonjour while OSC control is on.

   why: the lighting op can ride visual intensity on a real fader, next to the room's dimmers.

5. If there's a setlist: AbleSet

   Playing with Ableton + AbleSet? Use AbleSet's OSC Tracks to send Luxaudica a cue or look recall per song and per section — map it once, with the show file. Reading AbleSet's setlist feed with no mapping at all is in development.

   why: the chorus look arrives with the chorus, every night, without an operator.

6. If there's timecode: chase it

   Preferences → Chase MIDI Time Code or Chase Art-Net TimeCode. Once the clock locks, it owns the playhead and the show hits its marks with the desk; if the clock stalls, the show holds rather than drifting. Without a clock the show runs its own: hold times, crossfades, and GO from the panel, a MIDI pad or OSC. LTC is in development.

   why: a chase that is armed and never locks looks exactly like a chase that is off — check the connections canvas for the lock before doors.

7. Build the show file

   Cues in order, hold times set, crossfades chosen. Loop for installations; linear for a program. Play it once end-to-end at the venue.

   why: the rehearsal you skip is the transition that fails.

8. Set the safety net

   Map Blackout and Panic to physical keys/pads at front of house. Test both. Consider Reduce flashing for the room's sight-lines.

   why: when someone shouts "kill the wall", the answer is a reflex, not a menu.

9. Document the rig

   Screenshot the connections canvas and drop it in the show folder.

   why: next month's tech (possibly you) rebuilds this in minutes instead of re-deriving it.

Reference — what speaks what

• OSC in: every control, scene/look recall, blackout, panic — the full map is on the OSC reference.
• AbleSet: OSC Tracks → cue & look recall per song/section.
• Reaper: transport awareness — in development.
• DJ software: deck-aware beat/track info can drive the lock.
• Timecode: MIDI Time Code or Art-Net TimeCode drives the show clock; both opt-in in Preferences.
• MIDI: learn on any control; clock for tempo; pads for looks; keys for transport.

Deeper wiring diagrams live on the Learn page — the "Where it sits in your rig" section shows the four standard topologies with cabling.