When It Goes Wrong: Handling Technical Disasters Like a Professional

Early in my career — genuinely early, late nineties, playing a club in Toronto — I managed to knock my gear bag into the main breaker for the venue’s speaker system. I’d positioned the bag against the wall in the booth without checking what was on that wall, and sometime in the first hour I bumped it trying to reach for something. The room went silent at about the same moment as the bass should have dropped on a track I’d been building toward for the previous eight minutes.

The silence lasted about three seconds before I realised what I’d done. I reset the breaker, the system came back, I apologised on the mic with one sentence, and I went back to the music. The venue owner came to the booth afterward and said it was fine and that they were going to secure the breaker panel. They booked me back. I’ve told the story dozens of times since because it’s funny now and because it contained a lesson I’ve carried: the recovery matters more than the incident.

What Actually Goes Wrong and Why

Technical failures in live DJ performance fall into a few broad categories, each with its own most-likely causes and most-effective responses.

Equipment failure — a CDJ refusing to mount a USB drive, a mixer developing an intermittent connection, a laptop crashing — is the category most DJs fear and the one most reducible through preparation. The three USB drives I carry to every gig aren’t paranoia; they’re the result of having had a drive fail at an inconvenient moment more than once. A backup audio interface, a spare cable for the connection most likely to cause trouble, a secondary system that can play a track long enough to diagnose and fix the primary — these things cost less than the booking they might save.

Sound system issues — feedback, loss of signal to specific speakers, input routing problems — are usually the sound engineer’s domain but can involve the DJ. Knowing how to check your basic signal chain quickly, how to identify where a signal is dropping, and most importantly knowing when the issue is yours versus the venue’s, saves precious seconds during a live set.

Human error — knocking equipment, triggering the wrong track, losing sync at a visible moment — is the category that happens to everyone and the one most people are least prepared to handle gracefully, because it involves the ego as well as the practical problem.

The Sound Check Is Not Optional

The majority of technical problems that surface during a live set could have been identified during a sound check. A sound check is not about warming up your hands or checking that the music is loaded. It’s a systematic test of every component in your signal chain in the actual environment where you’ll perform.

Test each CDJ independently. Test the mixer’s channel routing. Test the headphone cue at different positions. Test the monitor levels in the booth. Test your laptop connection if you’re using one. Ask the sound engineer to confirm they’re receiving clean signal and that the levels are appropriate for the room. Do this at performance volume, not at a quiet test level, because some problems only manifest when the system is properly driven.

I’ve declined to play a venue on two occasions because the sound check revealed a problem they couldn’t resolve before doors opened. Both times I had a conversation with the promoter, explained the specific technical issue, and offered either to reschedule or to accept a reduced fee if they could fix the problem before showtime. Neither situation was ideal, but both were better than performing on a system with a known fault and pretending it wasn’t there.

When the Recovery Goes Right: Fred Again at Boiler Room

The moment that circulated widely from Fred Again’s Boiler Room set wasn’t a technical failure — it was an accidental music pause caused by an overenthusiastic fan touching equipment. What was notable about it was Fred’s immediate response: he handled it with genuine lightness, reconnected with the crowd rather than retreating into the technology, and got back into the music in a way that felt like it had just happened rather than like he was recovering.

What he demonstrated in that moment is a specific skill that’s harder than it looks: the ability to distinguish between what the crowd is experiencing and what you’re experiencing. As a performer in a technical crisis, the internal experience is usually some version of panic, embarrassment, and a strong desire to fix the problem immediately. The crowd’s experience, from the outside, is usually curiosity and then either sympathetic engagement or quiet frustration, depending on how you handle it.

The response that serves the crowd is the one that acknowledges the moment without amplifying its significance. A brief, genuine acknowledgment. A light touch of humour if the moment genuinely supports it. A return to the music as quickly as the actual problem allows. What doesn’t serve anyone is visible distress that makes the crowd feel anxious, or silence that lets the interruption fill the space indefinitely.

The Grimes Example: What Happens When the Recovery Doesn’t Land

Grimes’ Coachella 2024 performance attracted significant discussion not primarily because of the technical difficulties — these happen to everyone — but because the response to them appeared to minimise the problem in ways that didn’t serve the audience in the room. Laughter at technical difficulties can be a genuine and effective way of releasing tension. It can also read as indifference to the crowd’s experience, particularly at a high-profile show where people have invested significantly in being there.

The distinction between these two readings depends on how the humour is deployed and whether it’s accompanied by genuine effort to resolve the situation. Humour that says “I see this, I’m okay with it, let’s keep going” is different from humour that seems to say “I see this, it’s fine, nothing needs to change.” Grimes subsequently acknowledged the performance in her next show in a self-aware way that landed better — because by then there was something to have moved on from, rather than a problem that was still ongoing.

The lesson for working DJs isn’t specifically about humour. It’s about reading what the crowd needs from you in a moment of difficulty, which is the same skill you’re using to read what they need from you when everything is going well.

After the Incident: The Learning That Has to Happen

Every technical problem in a live set is data. After the gig, when the adrenalin has cleared and you’re in a position to think about it calmly, the failure deserves honest analysis. Was this something that the sound check should have caught? Was it a backup failure that a redundant system would have prevented? Was it human error that had a specific cause you can address? Was it a venue infrastructure problem that you should have raised with the promoter before agreeing to play?

The analysis has to be honest rather than exculpatory. The temptation after a technical failure is to attribute it to external factors — the venue, the equipment, the sound engineer — rather than to the parts of your preparation or response that you actually control. External factors are sometimes genuinely responsible. More often the failure was at least partly preventable from your end, and the point of the analysis is to identify what you’d do differently next time.

The best DJs I know have very clear mental libraries of their own worst moments, not as sources of ongoing shame but as references for their preparation process. The thing that went wrong in Seoul in 2015 is why I carry a specific cable that I’ve never needed to use since but that I check every single time I pack my DJ bag. The near-disaster at a festival in 2018 is why I arrive at venues with more time to spare than seems strictly necessary. The failures teach, if you’re willing to let them.

---

Frequently Asked Questions

How should a DJ handle technical problems during a live set?

Acknowledge the moment briefly and genuinely, without amplifying its significance. Use light humour if it fits the situation, but don’t use humour as a substitute for resolving the problem. Get back to the music as quickly as the technical situation allows. The crowd’s experience during a technical problem is shaped more by how you respond than by the failure itself.

What technical issues should DJs prepare for at every gig?

USB drive failures — always carry two or three. Signal chain interruptions — know how to identify quickly where a signal is dropping. Equipment compatibility issues. Power surges or outages — know where the breaker is before you need it. Human error — have a recovery plan rather than a freeze response when something goes wrong in front of a crowd.

How important is the sound check for preventing technical failures?

Very. The majority of technical problems that surface during a live set could have been identified during a systematic sound check. Test every component of your signal chain at performance volume, not just at quiet test levels. Ask the sound engineer to confirm they’re receiving clean signal. A thorough sound check is not preparation time; it’s performance insurance.

Should DJs use humour when something goes wrong at a gig?

Sometimes, with care. Humour can release tension and demonstrate confidence in ways that help the crowd stay engaged during a problem. But humour should accompany genuine effort to resolve the situation, not substitute for it. The difference between “I see this, let’s keep going together” and “this isn’t a big deal” is significant, and crowds feel it even if they can’t articulate why.

What can DJs learn from technical failures?

Honest analysis of what happened and what preparation would have prevented it. Every technical failure is data: was it something a sound check should have caught? A backup failure that redundancy would have prevented? Human error with a specific identifiable cause? The analysis has to be honest rather than exculpatory to be useful for future preparation.