Blog Performance 9 min read

Festival Main-Stage Gamepad Rig — Redundancy + Backup

A festival main-stage gamepad rig with full redundancy — two DualSense pads, USB-C primary, Bluetooth hot spare, two laptops, one failover plan.

By Aidxn Design

A festival gamepad rig is not a bedroom rig with a longer cable. It is a redundancy exercise dressed up as a performance. You have 45 minutes, 30,000 people, a stage tech who has never seen a DualSense before, and absolutely zero opportunity to say "give me a sec, the Bluetooth dropped". If the controller is the rig, the controller must be doubled. Here is how to build a main-stage gamepad rig that survives stage hands, crew radios, sweat, beer, and the inevitable moment a USB cable gets stepped on.

TL;DR
  • Two pads, two laptops, two paths: primary DualSense on USB-C to laptop A, spare DualSense paired over BLE to laptop B.
  • Ableton Link over a wired switch keeps both machines locked at the same BPM with sub-3 ms drift.
  • Failover target: swap to the spare and back into clip within two bars (~3.6 seconds at 132 BPM).
  • No festival Wi-Fi. Wired clock, wired MIDI, wired everything. Treat 2.4 GHz as radioactive.

What "redundancy" actually means at festival scale

Bedroom redundancy is "I have a spare cable somewhere". Festival redundancy is a written matrix where every component on the signal path has a named backup, the backup is already powered up, and the swap is rehearsed enough that you can do it in the dark. A DualSense is one of the most reliable controllers ever shipped — Sony moved over 80 million of them by mid-2026 — but reliability is a probability, and at 30,000 people that probability turns into "when", not "if". You build the rig assuming the pad will fail mid-set, because once a year it will.

The rig — gear list with specs

SlotItemSpecFailure plan
Primary controllerDualSense (white, labelled "A")USB-C tether, 2 m braided, right-angleSwitch to controller B on BLE
Spare controllerDualSense (black, labelled "B")Pre-paired BLE, fully charged, always poweredCharging dock under riser
Primary laptopMacBook Pro 14" M3Ableton Live 12, IAC Bus "RIG-A"Mirror laptop B
Mirror laptopMacBook Pro 14" M3 (identical)Ableton Live 12, IAC Bus "RIG-B"Identical project, Link-synced
Audio interfaceRME Babyface Pro FSTwo pairs of XLR out to FOHUA Apollo Twin X on standby
ClockAbleton Link over Cat6Gigabit unmanaged switch, no DHCPMIDI clock over USB as fallback
PowerTwo 200 Wh power banks + UPSBoth laptops on UPS batteryStage power outage = 25 min runtime
Bridge softwareUniversal Controller MIDIv1.0+, identical preset on both MacsPreset exported to USB key in case

Why USB-C is primary, BLE is the spare

Festival sites are a 2.4 GHz nightmare. Crew comms, photo triggers, lighting talkback, the punter livestreaming from row two — every one of them is dumping packets into the same band Bluetooth uses. BLE on a DualSense holds up surprisingly well, but "surprisingly well" is not a number you want underwriting a main-stage set. Wired USB-C gets you ~3 ms input-to-MIDI latency, zero RF exposure, and power as a side effect. The battery cannot die because the laptop is feeding it. The Universal Controller MIDI bridge handles either path identically so the swap is invisible from Ableton's side.

Mirroring the set across two laptops

Laptop A is the truth. Laptop B is a clone with one MIDI input remapped — instead of listening to IAC Bus "RIG-A", it listens to "RIG-B" which gets the spare DualSense's output. Both machines run the same Ableton project, the same drum racks, the same plugin instances. The trick is keeping them in sync at the bar level, not just the millisecond level. That is what Ableton Link is for, and it works beautifully over a wired LAN.

# Mirror laptop bootstrap (run on B before doors)
# 1. Pull latest project from primary
rsync -av --delete /Volumes/RIG-A/Live\ Sets/ ~/Music/Live\ Sets/

# 2. Confirm identical bridge preset
diff ~/Library/Application\ Support/UniversalControllerMIDI/preset.json \
     /Volumes/RIG-A/preset.json

# 3. Join Ableton Link group (wired only)
networksetup -setairportpower en0 off   # kill Wi-Fi entirely
# Wired Ethernet picks up Link automatically once Live is open

# 4. Arm tracks, leave faders down
# Mirror is silent until pad B takes the channel

The redundancy matrix — what fails, what saves you

FailureSymptomRecovery timeAudience hears
USB-C cable stepped onPad A drops out<2 bars, swap to pad BNothing — Link keeps tempo
Pad A stick-drift mid-sweepFilter glitches1 bar — bridge auto-deadzonesOne off-beat warble
Laptop A kernel panicAudio cuts4 bars — FOH crossfade to BBrief dropout, then back
BLE pad fully deadSpare unusable0 — primary still healthyNothing
Stage power outageBoth laptops on UPS0 for 25 minNothing for 25 minutes
FOH crew unplugs wrong cableHalf the signal goesFOH problem, not yoursBrace

Soundcheck drill — rehearse the failure

Most rigs never get tested in failure mode until the failure happens live. Don't be most rigs. During soundcheck, run the actual swap sequence: while music is playing, unplug pad A's USB-C cable and confirm pad B picks up. Time the recovery. Then plug A back in, swap back to A. Do it twice. The second time should be muscle memory. If you can't do it without thinking, you can't do it at 30,000-people-staring volume either. Sound on Sound's touring electronic rig guide covers the broader discipline if you want a deeper reference.

The flight case — labelled, taped, idiot-proof

At 3 AM after the show, the festival tech is going to repack your case. He has not slept in 19 hours. He does not know what a DualSense is. Make it impossible to misplug. Velcro every cable to its port. Colour-code USB-C tips (red = pad A, blue = pad B). Print a one-page rig diagram and tape it inside the case lid. Print a second copy and hand it to the stage manager. The diagram should fit on A4 and be legible from 1 m. If it isn't, simplify the rig — not the diagram.

Pre-show checklist (the one you actually print)

  • Both pads charged to 100% — confirmed on bridge UI before doors.
  • Both laptops at 100%, UPS at 100%, both plugged in.
  • Ableton Link shows "2 peers" on both machines.
  • Wi-Fi off on both laptops (airport en0 off).
  • Test tone sent to FOH. FOH confirms both XLR pairs.
  • One full failover drill done within the last hour.
  • Cue sheet handed to FOH and stage manager.
  • Bridge preset exported to USB key, taped inside flight case.

Festival main-stage isn't where you discover a bug in your rig — it's where you find out whether your soundcheck was honest. Build the redundancy, run the drill, then go and play the set. Universal Controller MIDI handles the pad swap; you handle the swagger. For the in-set "the pad just died, swap now" workflow, the hot-swap controllers mid-song guide walks the keystrokes. For the disconnect-detection logic that triggers the swap automatically, read the disconnect fix for live sets. And if you're back from the homepage wondering whether the bridge is gig-grade — it is. That's the entire point.

Keep reading

More setup walkthroughs