Resolume does not care what is on the other end of a MIDI cable. It sees a port, a channel, and a stream of notes and CC — the same way whether that stream came from an APC40 or from the Xbox controller that has been sitting under your telly since the weekend. That is the whole trick to using an Xbox controller in Resolume: you are not teaching Resolume about gamepads, you are handing it a MIDI source that happens to be fed by one.
Most gamepad VJ guides assume a DualSense, because the touchpad makes for a better screenshot. This one does not. An Xbox pad has no touchpad and no adaptive triggers, and it is still an excellent VJ controller — arguably the better one for touring, for reasons that have nothing to do with features.
- What you do: install the bridge, open a virtual MIDI port, enable it in Resolume, then MIDI-map clips and effects.
- What you need: any Xbox pad, Resolume Arena or Avenue, macOS 12+ or Windows 10+.
- Time: about 10 minutes to a deck you can play without a mouse.
- The trade: no touchpad XY, but better battery and build than a DualSense.
Why use a gamepad instead of a grid controller?
An APC40 or a Launchpad is a better clip grid than a gamepad will ever be. If your set is mostly "fire the right clip out of sixty-four", buy the grid. The honest comparison is in gamepad vs Launchpad and APC40, and it does not conclude that the gamepad always wins.
Where a pad does win is the combination of continuous control and eyes-up operation. Both analog triggers sweep across their full pull, so a crossfade or an effect intensity can ride underneath clip launching with the same hand. Most grid controllers give you buttons and a handful of faders you have to look down to find. A gamepad gives you sixteen inputs your thumbs already know by muscle memory, in a dark booth, with no light on the desk.
The second argument is logistical. A spare pad costs almost nothing, weighs almost nothing, needs no power supply, and fits in the laptop bag you are already carrying. That is a real backup rig rather than a theoretical one.
What does an Xbox pad lose against a DualSense?
Three things, and it is worth being straight about them before you build a mapping around hardware you do not have.
- No touchpad. This is the big one for VJ work. The DualSense touchpad gives a Kaoss-style XY surface on CC 16 and 17, which is genuinely the best single input a gamepad offers for effects — see the touchpad XY guide for what you are giving up. On an Xbox pad, the right stick is the closest substitute, and it springs back to centre, which is a meaningfully different feel.
- No adaptive triggers. No resistance feedback, and no haptic cue when a parameter hits its limit.
- No gyro. Motion control is off the table entirely.
What you get back: the Xbox pad has the better battery life, the more durable build, and a d-pad that holds up to being hammered. For a touring rig that lives in a flight case, that is not a small thing. The blunt version is in the Xbox Series setup guide: boring and reliable is a feature.
If you have an Elite Series 2, you also get four rear paddles, which are the closest thing a gamepad has to a second layer of buttons. Mapping the paddles is worth doing before anything else — they are the inputs your fingers can reach without moving your thumbs off the sticks.
Setting up the MIDI route
Resolume lists MIDI and OSC sources. An Xbox controller is an XInput device on Windows and a GameController device on macOS, so it does not appear in either list until something translates it. That is what the bridge does.
macOS
Open Audio MIDI Setup, choose Window → Show MIDI Studio, double-click IAC Driver and tick Device is online. That bus is what carries the controller into Resolume. macOS recognises Xbox pads natively from version 11 onward, so there is no driver to install.
Windows
Windows registers Xbox controllers as XInput devices automatically. For the MIDI side, the bridge ships a bundled virtual port. If that driver is blocked from registering — MSIX sandboxing and some EDR agents both do this — route through an existing output such as a loopMIDI port instead. The GameInput versus XInput breakdown covers which driver path you land on and why it matters.
One Bluetooth caveat worth knowing before a gig: only Xbox Series pads and the post-2016 Xbox One S revisions speak standard Bluetooth. Older Xbox One controllers use the proprietary Xbox Wireless protocol and need Microsoft's adapter, or a cable.
A mapping that actually survives a set
The mistake most people make is mapping everything. You end up with sixteen bindings you cannot remember under pressure. A set mapping should be small enough to recall in the dark.
| Input | MIDI | Job |
|---|---|---|
| A / B / X / Y | Notes 60, 62, 64, 65 | Four clip triggers — the row you live on |
| D-pad up / down | Notes 78, 80 | Walk the deck up and down without a mouse |
| D-pad left / right | Notes 81, 79 | Previous / next column |
| LT | CC 1 | Deck crossfade |
| RT | CC 2 | Master effect intensity |
| Right stick X / Y | CC 5, CC 6 | Two effect parameters, the XY substitute |
| LB / RB | Notes 67, 69 | Blackout and clip clear — the panic buttons |
Note what is not mapped: the left stick, the clicks, the menu buttons. Leaving inputs empty is deliberate. A stick you never touch is a stick that never fires something unexpected when you pick the pad up off the table.
When should you use OSC instead of MIDI?
MIDI gives you 128 CC numbers per channel. A small composition never hits that ceiling. A big Arena composition with layered effect racks hits it faster than people expect, and once you are juggling CC numbers on a spreadsheet, you have outgrown the protocol.
OSC addresses parameters by name over the network instead, which removes the numbering problem entirely. It is a Pro feature in the bridge. OSC vs MIDI from a gamepad walks through which one to reach for and when, and the honest answer for most Resolume rigs is MIDI first, OSC when the composition grows.
Can this drive the lighting rig too?
Not directly, and it is worth being precise because people assume otherwise. The bridge outputs MIDI, plus OSC on Pro. It does not output DMX or Art-Net.
What people usually mean by "gamepad to lighting" is a chain: the pad drives Resolume, and something downstream of Resolume converts to DMX. The Resolume to Lumen to DMX chain lays that out properly. The pad is at the top of the chain, not wired to the fixtures.
Taking it to a gig
Three things, learned the boring way.
- Wired, always, for anything paid. Bluetooth pairing is the single most likely thing to fail at the worst moment, and a USB cable removes the entire category of problem.
- Save the preset as JSON and carry it. The bridge stores mappings as plain JSON, so the show laptop loads the same CC numbers and curves as the machine you built the set on. Resolume stores its side with the composition.
- Map the panic buttons first. Blackout and clip clear on the shoulders, before anything creative. You will use them.
If you also produce, the same pad and the same preset work in a DAW — see the Xbox controller in Ableton Live guide, or the Resolume hub for every VJ guide in one place.
The controller in your bag is already a sixteen-input VJ surface with two continuous triggers. Universal Controller MIDI is the bit in between — free to try on Mac and Windows, with custom mapping and OSC on Pro.