The same light show in fifty-five different buildings
A crowd light show for the Mixtape Tour - New Kids on the Block with Salt-N-Pepa, Tiffany and Debbie Gibson - pulling the audience into the production itself across fifty-five dates. Doing it once is a technical problem. Doing it identically every night, in a different arena each time, is a different one.
- 55
- Tour dates
- A different building every night
- Placement
- Per-venue variable
- A load-in task, not an engineering one
- None
- Network required
- No cellular, no WiFi, no pairing
- iOS + Android
- Platforms
- One broadcast, both natively
The challenge
A tour is not one show repeated. It is fifty-five load-ins to buildings with different steel, different concrete, different rigging positions and different everything else, and the production has to look the same in all of them.
That is unforgiving for anything running at 2.4 GHz. Radio behaves differently in every room, and a crowd is not a neutral audience for it - bodies absorb these frequencies, so a full arena is measurably harder than the empty one the crew set up in that afternoon. Whatever worked at sound check has to still work when twenty thousand people are standing in the path.
And the schedule is the real constraint. There are hours between the trucks arriving and the doors opening, no opportunity to iterate, and a hard deadline that does not care. A system that needs tuning per venue does not survive a tour - not because tuning is difficult, but because there is no night on which there is time for it.
What we did
The design goal was to leave exactly one variable per venue, and make it a physical one.
Nothing about the audience is configured: a broadcast reaches whatever is in range and listening, with no pairing, no registration and no per-device setup, so twenty thousand people need the same preparation as one. The show content lives in the app rather than travelling over the air, so what is broadcast is a small cue rather than a payload, and the same cues drive the same effects in every city.
That leaves coverage, which is a question of where the hardware goes in this particular room. It is a load-in task rather than an engineering one, and it is the only thing that changes between Tuesday and Wednesday.
The other decision that mattered was optimising for the worst building rather than the best. A tour is judged on its floor, not its ceiling: a show that is spectacular in one arena and patchy in another is worse than one that is good in all fifty-five, because the audience in the fifty-fourth city has no idea what it looked like in the first.
The outcome
Fifty-five dates with the audience as part of the production rather than spectators to it, across a four-act bill.
The honest limits are the same ones this approach always carries. It reaches phones that have the app and are in range, so coverage follows installs and hardware placement, and it varies room to room. The channel is one-way, so nothing reports back about what was received on any given night.
The transferable part is about what repeatability costs. The instinct with a system like this is to tune it for each room, and the result is a rig that works brilliantly when someone knowledgeable is standing next to it and unpredictably when they are not. Designing so that only one variable changes per venue gives up some peak quality and buys back the thing a tour actually needs, which is the same show tonight as last night.
