Hippotizer Gamepad Show Control with a DualSense

Hippotizer is the Green Hippo media server you find behind half the touring concert visuals on the planet. It is programmed through Zookeeper, the desktop control app, with pins, masters, multicontrollers, and a MIDI Map editor that is mature, native, and underused for prototyping. A DualSense bridged through virtual MIDI into Zookeeper gives a programmer fast tactile control during show build — without occupying a real desk while another op is on it. This walkthrough covers the Hippotizer gamepad MIDI setup end to end.

Why a gamepad for Hippotizer

Show programming on Hippotizer is a two-stage process — build the show with pins, masters, and multicontrollers, then hand the show to an operator on the desk. During the build stage a programmer wants a controller that doesn't compete with the operator's desk. A DualSense covers that — two sticks for pin nudging, four face buttons for state jumps, triggers for masters. Universal Controller MIDI publishes it as a virtual MIDI port Zookeeper consumes through its native MIDI Input device.

What you'll need

• Universal Controller MIDI v1.0+ (download)
• Hippotizer V4+ with Zookeeper
• Windows 10+ on the Hippotizer host node
• PS5 DualSense on USB-C

Setup

1. Bridge the controller on the host

Install the bridge on the Hippotizer host PC. Launch it, plug the DualSense in over USB-C. The bridge ships a Windows kernel virtual port — no loopMIDI needed. Confirm the port appears in Settings → System MIDI as Universal Controller MIDI.

2. Add the MIDI Input device in Zookeeper

Open Zookeeper, switch to Configuration → Devices. Add → MIDI Input. In the device's parameters set Source = Universal Controller MIDI and Active = true. Apply. The device's incoming-data indicator should blink as you wiggle sticks.

3. Learn bindings via the MIDI Map editor

Open Configuration → MIDI Map. Right-click any pin or master in the map editor. Pick Learn. Wiggle the gamepad input. The mapping is captured. Repeat per binding. Pins, masters, mixer faders, and multicontroller cells are all valid targets.

4. Build a gamepad-specific Multicontroller page

Open the Multicontroller. Build a page with the controls you want gamepad-driven — a master, a couple of pin sets, a state flip. Learn the bindings from the gamepad. Now you have a dedicated gamepad page you can switch into during programming and out of when handing the show off.

Mapping ideas

• Left stick → pin X/Y nudge. CC 1/2 onto a 2D pin pair, with tight MIDI Min/Max for sub-pixel control.
• Right stick → camera / scene rotation. CC 3/4 onto a Notch Block's camera pin pair.
• Triggers → master / submaster fades. CC 5/6 onto layer or output masters.
• Face buttons → state flips. Notes 60–63 onto Cue Triggers in a Programmer state.
• Touchpad → FX 2D parameter. CC 16/17 onto a Notch Block FX pin pair.
• D-pad → Multicontroller page nav. Notes 78–81 step through pages.

Performance tips

• 14-bit CCs on pin pairs. Enable 14-bit in the bridge. Hippotizer's MIDI Map reads MSB/LSB pairs and pins ramp smoothly across 16k values instead of 128.
• Bound MIDI Min/Max per pin. Pins driven across their full range from a stick are too coarse. Bound the binding to ±10% of the pin's range for nudge-style control.
• Use Pickup mode. In each binding's settings, enable Pickup so pins don't snap when the stick is wiggled for the first time.
• Keep the gamepad on a programming page only. Don't bind it across the global MIDI Map — keep it scoped to a Multicontroller page so it doesn't interfere with the operator's desk.

Gotchas

• Zookeeper doesn't see the port. The MIDI Input device enumerates ports on add. Run the bridge first, then add the device.
• Pins snap when wiggling sticks for the first time. Enable Pickup mode per binding.
• Notes fire twice. If you wired both note-on and a separate state trigger, remove one.
• MIDI lag with heavy GPU loads. Hippotizer's media engine can saturate the host. MIDI input runs on a separate thread but Zookeeper's UI cooks on the main thread — pin updates may lag visually even if values are correct. Watch the OSC log to confirm values are landing.
• Don't ship the gamepad to a show desk. This is a programming-time tool. The operator runs the desk. The gamepad goes back in the laptop sleeve before doors.

Wrap

Hippotizer plus a DualSense plus virtual MIDI is the programming-time pocket tool you wish you had on the last build. Multicontroller pages are the right scope for gamepad bindings — they keep the controller out of the operator's surface and inside the programmer's workspace. Green Hippo's Hippotizer support docs cover the rest of the show-control side.

Try Universal Controller MIDI free on a Hippotizer host tonight. $49 Pro unlocks every connector and the mapping editor.