An arena tour gamepad rider line item is not a meme. Several touring acts have quietly added a DualSense or Xbox Series controller to their show-control spec — for B-stage scenic cues, FOH-side QLab macro fire, or as a backup show-control surface alongside the main console. The catch is the same as any rider line: vague language gets you a $40 third-party clone with 18 ms of input delay. Precise language gets you the exact unit the show file expects.
- Spec the model number (CFI-ZCT1W for DualSense, not "PS5 controller").
- USB-C only, 3 m braided. Bluetooth banned on the show feed.
- Pin the bridge version (Universal Controller MIDI v1.3.0+). Auto-update disabled.
- Two spare units + one spare cable on the audio cart, labelled.
- Document the test procedure, including pass/fail criteria, in the rider itself.
Why a gamepad is on a rider at all
Show control has used MIDI surfaces forever. The Akai MPCs of the 90s. The Behringer X-Touch of the 2010s. The JLCooper MCS-3000. They share a job: present an array of buttons, faders, and continuous controllers, and emit MIDI events that the show file maps to cues. Gamepads do the same thing, with two real advantages: they are cheap enough that spares are trivial, and they are ergonomic for cue-fire scenarios where the operator is also doing other things.
Touring acts have started to use them in two places: backstage B-stage scenic cue fire (the production manager can carry one in a pelican to anywhere on the floor), and FOH-side macro fire (a button on the gamepad fires a QLab macro that does sixteen things at once across audio, lighting, and video). Once they are in the show file, they are on the rider.
The rider language — copy-paste template
Below is the actual block we have shipped on tours. Names redacted, model numbers and version pins real.
# ────────────────────────────────────────────────
# SECTION 7.4 — SHOW CONTROL — GAMEPAD SURFACE
# ────────────────────────────────────────────────
7.4.1 CONTROLLER UNIT
Sony DualSense, model CFI-ZCT1W (white) or CFI-ZCT1W A02 (black).
Quantity: ONE (1) for active use.
Spares: TWO (2) units of the same model on the audio cart.
Edge variant (CFI-ZCT1J) is acceptable as a spare but not preferred
as primary due to detachable stick modules.
7.4.2 CABLING
USB-C to USB-A, 3.0 m, braided, e+ shielded.
Anker A8633 or equivalent.
ONE (1) on the controller, ONE (1) spare on the audio cart.
Bluetooth pairing is NOT permitted for the show feed.
7.4.3 HOST
Apple Mac mini M2 (8 GB minimum), running macOS 14.4 or later.
Dedicated show-control Mac. Not shared with FOH or MON desk PC.
Power: 1 × IEC C13, isolated audio cart circuit.
7.4.4 SOFTWARE — BRIDGE
Universal Controller MIDI, version 1.3.0 or later.
https://controller-midi.aidxn.com
Auto-update DISABLED. Telemetry DISABLED.
License key pre-loaded by production. Do not re-license on site.
7.4.5 SOFTWARE — SHOW FILE
Signed mapping profile delivered by production at advance.
Local crew loads only. No modifications permitted on site.
SHA-256 of profile printed on the rider attachment.
7.4.6 TEST PROCEDURE
10 minutes minimum, completed during the FOH/MON soundcheck window.
See appendix 7.4.A for pass/fail steps. Both FOH and MON ops sign off.
7.4.7 POSITION
Audio cart, downstage-left, within reach of the show-control op.
Cable strain-relieved to the cart leg with gaffer. Why the spec is this picky
Every line in that block exists because something went wrong on a previous tour. The model number line is there because someone supplied a PowerA wired controller that emits the same USB HID profile but has 22 ms of input latency vs. the DualSense's 4 ms. The auto-update line is there because the bridge updated mid-show on one tour and changed a deadzone default. The cable line is there because non-braided cables shed pins around metal flight cases.
Riders are not paranoia — they are the failure history of the production written down so the next tour does not repeat it.
The test procedure
Show-control gear on a rider needs a test procedure with pass/fail criteria. This is the appendix that goes with the section above.
| Step | Action | Expected | Pass/Fail |
|---|---|---|---|
| 1 | Plug DualSense into audio cart Mac via USB-C. | Bridge UI shows "Connected — CFI-ZCT1W". | Hardware |
| 2 | Load show mapping profile. | SHA-256 matches rider value. Profile active. | Software |
| 3 | Press Triangle. | QLab fires cue 1.1, lighting cue 1.1, video cue 1.1 simultaneously, < 8 ms skew. | Integration |
| 4 | Hold L2 fully. | FOH-bound CC 11 reaches 127 within 30 ms of full depression. | Analogue |
| 5 | L1+R1 held 500 ms. | Show-stop macro fires. Audio fade, lights to house, video to black. | Safety |
| 6 | Unplug USB-C, replug. | Bridge auto-reconnects within 3 s, profile remains loaded. | Recovery |
| 7 | Power-cycle audio cart Mac. | Bridge autostarts, profile loads, controller re-detected without manual intervention. | Boot |
Every step needs an FOH or MON tick before the show goes live. Steps 5 and 7 are the non-negotiables — if the safety stop does not fire reliably, the gamepad does not run the show.
Where the gamepad sits in the show file
Most tours that use a gamepad on the rider run it through QLab. The bridge emits MIDI; QLab listens; QLab fires the macro cue. Our QLab + DualSense post covers the actual mapping. The rider language above sits on top of that workflow.
For tours with significant lighting and video integration, the same gamepad MIDI feed can fan out to a Hippotizer media server or a DMX lighting console via a MIDI router. Each receiving system has its own line in the rider. Show-control on a tour is always a fan-out tree, not a single device.
Local crew tone — how to write it without being a jerk
Tour riders have a reputation for being aggressive. The gamepad line is new enough that local crews will not have seen it before, and tone matters when you want it to load in cleanly. A few rules:
- Explain the model number once. "DualSense (CFI-ZCT1W) — the official Sony unit, not a third-party clone, due to input latency variance."
- Provide the rider attachment with screenshots of the bridge UI in the correct state. The local IT/audio person has never opened it before.
- Name the version. "v1.3.0 or later" is friendlier than "must be exactly v1.3.0".
- Provide a number to call if anything in the spec is unclear. Most tour management has a production-tech hotline already.
Insurance, certification, and the production manager
Some venues require show-control gear to be PAT-tested (UK), C-Tick'd (AU), or UL listed (US). A consumer DualSense is fine on every standard we have run into, but cables are sometimes not — non-braided OEM cables from the box are usually PAT-passable but the gaffer-and-rigger braided cables we spec are not always. Provide certification paperwork with the rider attachment so the production manager does not have to chase it.
Put it on the rider, name the version, ship the test procedure. Then the local crew loads it the same way they load anything else — by following the spec. Universal Controller MIDI is the bridge half of that contract; the rest is paperwork.