3 Overlooked Lighting Console Mistakes That Ruin Shows
Last night, during the lead singer's emotional solo, the lights strobed like a cheap disco. That 2‑second glitch shattered the spell—and it was entirely avoidable.
I'll be honest: most people get these things wrong. They obsess over fixture placement and color palettes but ignore the invisible infrastructure that can torpedo a show in an instant. As a lighting director who's seen (and caused) my share of near-misses, I want to level with you about three critical mistakes that risk ruining your show's artistic impact—and exactly how to fix them before the next house lights go down.
Mistake #1: The Network Blind Spot
Here's the thing: your DMX network is not a magic pipe. DMX512‑A refresh rates top out around 44 Hz, and even 0.1% packet loss can produce visible stutter in fast‑moving fixtures. That's right—a tiny fraction of lost data will make your meticulously programmed mover look like it's hiccuping. Most technicians assume their sACN or Art‑Net rig is solid, but they never test under load.
A single unsegmented network can let a faulty node flood the entire rig with broadcast traffic. I saw this firsthand on a major pop tour where a Hog 4 console locked up mid‑set because a misbehaving node broadcast a storm of Art‑Net packets. The backup console took over, but for seven seconds the stage looked dead. The audience didn't know why; they just felt the energy drain.
Here's another blind spot: when you start converging video and lighting on the same network, you introduce failure modes that traditional DMX training completely ignores. A media server hiccuping on frame sync can suddenly spike latency beyond 30ms, and your moving lights start lagging visibly.
Mitigation starts with VLAN segmentation. Isolate lighting traffic from everything else. Put your consoles on a separate management VLAN. Run redundant backup consoles with active tracking, not just a cold spare. And before every show, do a full‑system stress test: spam cues, fire macros, yank a network cable while your busking operator keeps the look alive. If you can't survive that in rehearsal, you won't survive it on show day.
Mistake #2: The Corrupted Cue Stack
Let me level with you: your show file is a fragile thing. Improper USB ejection accounts for 31% of console support tickets, according to MA Lighting data. That moment when you rip the drive out to save ten seconds? You're gambling with the entire design.
But corruption isn't just about USB manners. I've watched a designer clone fixtures across a rig, only to have inherited values turn a blackout cue into a sudden strobe. The console did exactly what it was told; we just didn't realize what we were telling it.
The 2023 BAFTAs blackout is the ultimate cautionary tale. A corrupted macro pool on an MA3 caused a 15‑second dead stage right during a high‑profile award moment. For fifteen seconds, the broadcast cut to a wide shot of nothing. That kind of mistake erodes performer trust instantly. Dancers and singers learn to doubt the tech crew, and you'll never get that confidence back entirely.
The impact on artistry is real: when a console error plunges a key moment into darkness, the audience's emotional journey breaks. Designers start playing it safe, avoiding innovative programming because they fear the next crash. That's a quiet tragedy for our whole industry.
Fix this with a rigorous offline workflow. Program and visualize in blind before touching a real fixture. Save redundantly—local drive, cloud, and a thumb drive you never pull without ejecting. Implement a strict 'no‑pull‑without‑eject' discipline. And clone fixtures with caution: manually scrub all parameter sets after a clone to catch unintended values. A few extra minutes of checking can save a show.
Mistake #3: The Syntax Time Bomb
A single misplaced command can cascade into full‑rig failure. In one theatre production, an ETC Eos cue list contained a stray Out command that faded a critical scene to black. It wasn't caught in rehearsal because the operator manually bypassed it each time without noting the error. Come opening night, the automated run did exactly what we told it—and the scene died.
Accidental grand master zeroing or busking palette overrides can instantly kill a key moment. I once accidentally recalled a palette during a busking segment that overrode the lead singer's special with a deep blue backlight—right when she stepped to the front for her spotlight moment. She couldn't see the audience, I couldn't undo it fast enough, and the moment flopped.
Timecode drift and trigger misfires plague scripted shows when cue stacks aren't conditioned. If your timecode source wobbles by just a few frames, your tightly synced sequence becomes a train wreck. And in busking scenarios, operators frequently overwrite critical parameters by grabbing a palette that looked right on the touchscreen but carried hidden information like gobo or zoom.
Mitigation demands blind plotting and conditional triggers. Always test cues in blind first. Use conditional logic to prevent a grand master from accidentally hitting zero unless a confirm macro fires. Run dedicated disaster‑drill rehearsals: have someone deliberately trigger a blackout, and your busking operator must recover within three seconds while the band keeps playing. Some companies now employ dedicated busking operators whose entire job is risk management during live improvisation—because they know the hot‑shot LD can't watch everything at once.
The Invisible Difference
This week, segment your lighting network, verify your showfile backup protocol, and run a full simulation with a deliberate 'disaster drill.' The difference between a flawless show and a viral fail is often invisible—until the house lights go down. Don't let a corrupted cue stack or a network blind spot turn your art into a cautionary tweet.
