Blog
How to build a safe manual override layer for automated lighting
Keep automation, then add MIDI, a phone bank and desk merge so a human can still kill or take over the room.
WavePhase · 2026-08-23
Automation is not the last word
Reactive and scheduled lighting fails in public: a silent speech, a medical incident, a track that is all breakdown, a detector that hears the smoke alarm test. If a look cannot be stopped from a pad or a phone, it is not finished.
Build the automatic layer first so the room has a default. Then wrap it with overrides that always win. The override layer is the product the operator actually trusts.
The minimum viable override
Blackout. Master dimmer. Strobe enable (off by default). Haze. One “safe wash” pad that recalls a dim warm look and parks heads. That set covers almost every emergency and most “the owner just walked in” moments.
Put blackout on a physical control. Network-only kill is a second failure mode. If the laptop UI is full-screen on the wrong window, the pad still works.
How overrides should win
Decide the math. A blackout should multiply intensity by zero, not “try to fade.” A master fader should scale the automatic wash, not fight it with HTP in a way nobody can explain. A colour override should replace the automatic colour until released.
Gates on strobes belong in the automatic path and still sit under the strobe-enable pad. Two gates are correct. Zero gates are how you get a lawsuit and a headache.
Visiting desks can merge on DMX input if the software supports it. Reserve a universe or a takeover mode. Document who is the master when both systems are live. “We both sent something” is not a merge strategy.
Practice the unhappy path
In soundcheck, hit blackout. Confirm haze dies or stays — know which you chose. Confirm heads freeze or go home. Confirm the automatic layer returns cleanly when you release. If return is a surprise flash, fix the patch, do not hope.
Give the door person or floor manager a dead-simple instruction: “this button makes it dark.” You will not be at the laptop for every problem.
A test you can repeat
Automatic wash running. Speech. Override to safe wash. Speech ends. Release. Music. Transient accents return. Strobe enable stays off. That five-step loop is the whole quality bar for a club override layer.
Who holds the pad
If only the person who built the graph knows where blackout lives, you do not have an override layer. You have a hobby. Label the surface. Photograph it. Put the photo in the staff chat.
Owners will ask you to “make it less.” A master that actually scales the automatic layer lets you do that without pretending the room is reading the music. A bass envelope is a measurement. A fader is still the adult in the room.
Review the layer after the first busy Friday. Something will be wrong: haze on a momentary instead of latch, strobe enable that defaults on after a crash, a colour override that never releases. Fix those before you add more automation.
Merge without a fistfight
If a visiting desk must run, decide the merge before load-in. Options: they take the nodes and you sit out; they take DMX in on a reserved universe while you keep the wash; you take their desk as a MIDI/OSC surface only. “Both of us send universe 1” is not an option.
Write the choice on the house plot. The touring LD should not have to invent policy at 17:00. If you cannot merge cleanly, give them the nodes and a printed restore procedure for your PC IPs.
After they leave, verify house looks come back. Visiting files have a habit of leaving a node on the wrong universe. That is an override problem too: the house must be restorable without the original programmer.
Defaults after a crash
Decide what happens when the PC reboots mid-show. Last look held on the nodes is different from all channels to zero. Know which your nodes do. If they go dark, the override layer should include a “restore safe wash” that does not require the old session.
Strobe enable must default off after a restart. If a crash can leave strobes armed, you have a safety bug, not a taste issue. Test the reboot path once per install, not once per year.
Related
If you want this in software
WavePhase is a desktop lighting app: a node graph that can take live audio, time, MIDI, OSC or an API and send the result to fixtures, pixels and visuals over Art-Net or sACN. The articles on this blog teach the craft. The app is one way to run it.
Free Early Access includes the editor and one DMX universe. Features and the quick start are the product docs — not a substitute for patching real hardware.
Free account required — no credit card — Windows, macOS and Linux.