Museum Installation — Gamepad-Driven Interactive Sound

A working museum installation gamepad rig has nothing to do with playing games. It is the unglamorous middle layer between an autonomous generative soundscape that runs eight hours a day and a docent who occasionally needs to nudge it — quiet the room during a school visit, swap to a narrative scene for a tour group, kill the audio because a fire alarm just went off. The gamepad is the human-in-the-loop without committing to a custom hardware panel that takes six weeks to replace.

Why a gamepad belongs in a gallery

Sound art installations have run on physical interfaces for forty years — buttons, dials, foot pedals, sometimes touchscreens. The argument for a gamepad is boring and decisive: it is a known good consumer device, every museum tech has held one, and a replacement is at the corner shop. A custom-built MIDI panel by a friend-of-the-curator is romantic until the encoder fails three weeks into a six-month run and the artist is now in Berlin.

The other reason is range. Sixteen buttons plus two sticks plus two analogue triggers plus a touchpad is enough surface for any docent intervention you will ever need, and the form factor reads as "you can pick this up" — important when the docent on day one is not the docent on day forty-five.

The autonomy split — what runs without input

Design the autonomy first. The patch should be capable of running for eight hours with zero input and still sound considered. Use these defaults:

• Three or four generative scenes that crossfade every 18–22 minutes. Not on a clock — on a Markov-weighted random walk so visitors never hear the same transition twice.
• Bounded randomness on every parameter. Filter cutoff drifts between 800 Hz and 4 kHz over slow LFOs. Reverb decay drifts between 1.8 s and 4.5 s. Nothing should jump.
• A daily envelope. Open quiet, peak around 1–3 pm when the gallery is busiest, ease down toward closing. A single sine-wave master gain over the 8 hours works.
• A "silence rule" check. If the patch ever outputs RMS < -40 dB for 90 seconds, force-trigger a scene change. Dead air is the only true installation failure.

The docent layer — what the gamepad does

The docent override is small on purpose. Five or six controls. More than that and nobody remembers the layout by Wednesday.

Kiosk mode — locking the surface down

Out of the box the DualSense exposes PS, Share, Options, Mute, and the touchpad click as system inputs. In an always-on PC the Share button can pop up the PS5 capture dialog (or its OS equivalent), Options can summon a system menu, and the touchpad click is sometimes hijacked by the OS as a mouse button. None of that is acceptable in an unattended install.

Universal Controller MIDI ships a Kiosk profile. It is a whitelist — only the inputs you list emit MIDI, everything else is dropped at the bridge level before the OS sees it.

# /etc/universal-controller-midi/kiosk.profile

mode = "kiosk"

[whitelist]
buttons = ["triangle", "square", "cross", "circle"]
analogue = ["L2", "R2"]
touchpad = ["xy"]

[blacklist]
buttons = ["ps", "share", "options", "mute", "touchpad-click"]

[chord.emergency_stop]
trigger = "L2+R2"
hold_ms = 2000
emit    = "note 127 ch 1"
cooldown_ms = 5000

Crash recovery — the boring bit that saves the show

Eight hours is long enough that something will hang. The DAW or Pd will crash, the OS will pop a software-update dialog, a USB port will brown-out. Treat the install like a venue, not a laptop.

• Disable auto-update. Both OS and apps. Quarterly maintenance windows only.
• Disable sleep. Caffeinate on macOS, "High performance" on Windows.
• Disable notifications. Do Not Disturb permanently on.
• Supervisor process. A small shell script (or launchd / NSSM service) that monitors the audio host and restarts it if it exits.
• USB-C cable strain relief. Cable-tie to the desk. The most common failure is a curious visitor unplugging the gamepad.

# macOS supervisor — keep the audio host alive

#!/bin/zsh
APP="/Applications/Ableton Live 12 Suite.app"
SET="/Library/Installation/gallery_2026.als"

while true; do
  if ! pgrep -x "Live" > /dev/null; then
    /usr/bin/open -a "$APP" "$SET"
  fi
  sleep 30
done

Patch design — what works in galleries

A gallery soundscape is not a concert. The room has hard walls, marble floors, glass cases. Reverb stacks. Treat it as a wet space and pull back on your own effects.

• Mono more often than you think. Visitors walk past speakers, not sit between them.
• Limit the spectrum. A 200 Hz–8 kHz band is plenty. Sub frequencies in a gallery rattle the cases.
• Slow envelopes. Anything faster than 3-second attacks reads as foreground audio and competes with the art.
• Vary the density. Bake in two-minute silences. They feel composed, not broken.

Bind the bridge's touchpad-XY to a crossfade between two scenes, and the L2 trigger to master gain, and the docent can navigate the entire daily envelope with two fingers and a thumb. The rest of the rig is the patch. The Ableton MIDI mapping shortcuts still apply — gallery rigs are not special, they are just careful.

Why this pairs with the gallery soundscape pattern

This post focuses on the docent-intervention layer. The companion pattern — what the autonomous generative soundscape actually does and how visitor-presence sensing drives it — is in our art gallery generative soundscape post. Read both together if you are designing an install from scratch.

A DualSense plus Universal Controller MIDI plus a Mac Mini is roughly $800 of hardware for the docent layer of a real eight-hour-a-day sound install. Versus a custom MIDI panel build (~$3500 + six-week lead time), the gamepad wins on every axis that matters: replaceability, familiarity, and the speed from "this is broken" to "this is fixed".