The MPC workflow is pads, Q-Links and a sequencer — and all three of those accept generic MIDI. That means you do not need an MPC One on the desk to work the way an MPC works; you need something with buttons for the pads and something analogue for the Q-Links. A gamepad has both. This guide sets up MPC Software gamepad MIDI control with a DualSense, Xbox or 8BitDo pad, using Universal Controller MIDI to turn the HID stream into a MIDI port the MPC Software recognises.
- What you do: publish the pad as a virtual MIDI port, set it to Master in MPC's MIDI preferences, read the pad note numbers in Program Edit, match your bindings to them, MIDI Learn the Q-Links.
- What you need: MPC Software or MPC Beats, macOS or Windows, any supported controller, the bridge.
- Time: 12 minutes, assuming you read the pad notes instead of guessing them.
- The one thing people get wrong: pad MIDI notes are per-program and editable — check, don't assume.
Why a gamepad instead of an MPC controller?
Because the controller is the expensive half and the software is where the work happens.
MPC Software and MPC Beats run perfectly well without Akai hardware attached. The hardware is a beautiful set of velocity-sensitive pads and four touch-sensitive Q-Links, and if you have it, use it. But a gamepad covers eight pads, two genuinely analogue Q-Link substitutes, four navigation buttons, and a two-axis touchpad for about a tenth of the price of an MPC One — and it travels in a coat pocket.
There is also a specific thing a gamepad does better than an MPC: the analogue triggers. Q-Link knobs are touch-sensitive but they are still knobs, which means a sweep is a wrist movement. A trigger pull is a finger movement with a spring return, which is a much more natural shape for a filter sweep you want to snap back. It is the same point we made in the finger drumming workflow.
What you need
- MPC Software 2.x or later, or MPC Beats — macOS or Windows
- Universal Controller MIDI — download for your platform
- A supported gamepad — DualSense, DualShock 4, Xbox Series, Switch Pro, 8BitDo
- macOS: IAC Driver online. Windows: nothing extra
How do you get the gamepad into MPC Software?
Publish the virtual port, then set it to Master in Preferences → MIDI / Sync so it reaches programs and Q-Links rather than being treated as a passive input.
1. Create the port
On macOS: Cmd-Space, Audio MIDI Setup, then Window → Show MIDI Studio. Double-click IAC Driver, tick Device is online. On Windows the bridge installs a kernel-level virtual port when you run the installer — approve the driver prompt once.
2. Set it to Master in MPC
Launch the bridge, then MPC Software. Open Preferences → MIDI / Sync. The MIDI Input list has a mode popup against each device. Set UCM Bridge to Master. This matters: a port left on the default passive setting will feed recorded notes but will not reach the Q-Links or transport. Master is what you want for a controller.
3. Prove it works
Press a face button. The corresponding pad should light in the pad grid if the note matches. Pull the right trigger — if you have already learned a Q-Link, it should move. If nothing happens, check that the port is still set to Master; MPC occasionally resets this when a device is unplugged and replugged.
What MIDI note does each MPC pad respond to?
Whatever is set in Program Edit → Pad → MIDI Note for that pad in that program — it is editable per pad, and different factory programs use different assignments, so read it rather than assuming a standard.
This is where most "my gamepad does not trigger the pads" reports come from. People assume a universal MPC note map, bind their buttons to it, and then half the pads do nothing because the loaded program uses a different range. The fix takes thirty seconds:
- Open Program Edit and switch to the Pad tab.
- Click Pad 1. Read the MIDI Note field.
- Click Pad 2, 3, 4 and confirm they step upward by one, which most factory programs do.
- Note the first value. That is your root.
Then open the bridge's mapping editor and set your eight trigger buttons to a contiguous block starting at that root. Face buttons get the first four, the d-pad gets the next four. Alternatively, go the other way: edit the Pad MIDI Note fields in MPC to match the bridge's default notes. Both work — pick whichever you will remember in three months.
How do you control Q-Links from a gamepad?
Assign the parameter to a Q-Link first, then MIDI Learn that Q-Link and move the gamepad control you want on it.
Open the Q-Link Edit panel. Each Q-Link has an assignable target — a program parameter, a plugin parameter, a mixer level, or a project-level control depending on the Q-Link mode you are in. Assign the four you care about, then use MIDI Learn on each and move the matching gamepad axis.
The allocation that plays best:
- L2 trigger → Q-Link 1. Filter cutoff on the current program. The one you will ride constantly.
- R2 trigger → Q-Link 2. Drive, saturation or wet mix. Parks where you leave it.
- Left stick Y → Q-Link 3. Sample start, for chopping gestures. Springs back, which is what you want.
- Right stick Y → Q-Link 4. Send level. Push, hold, release.
The touchpad's two axes are worth keeping for plugin morphing rather than Q-Links, because the Q-Link panel only has so many slots and a touchpad is better used on something with two meaningful dimensions. The touchpad XY guide covers getting it calibrated.
Default mapping table for an MPC session
Assumes you have set a contiguous note block from 36 and the loaded program's Pad 1 MIDI Note matches.
| Control | MIDI message | Target |
|---|---|---|
| Cross / A Note 36 Pad 1 Kick — fixed velocity 127 | ||
| Circle / B Note 37 Pad 2 Snare — fixed velocity 110 | ||
| Square / X Note 38 Pad 3 Closed hat — fixed velocity 85 | ||
| Triangle / Y Note 39 Pad 4 Open hat — fixed velocity 95 | ||
| D-pad up Note 40 Pad 5 Clap | ||
| D-pad right Note 41 Pad 6 Perc / rim | ||
| D-pad down Note 42 Pad 7 Sub / 808 | ||
| D-pad left Note 43 Pad 8 Vocal chop | ||
| L2 trigger CC 1 Q-Link 1 Filter cutoff | ||
| R2 trigger CC 2 Q-Link 2 Drive / wet mix | ||
| Left stick Y CC 4 Q-Link 3 Sample start | ||
| Right stick Y CC 6 Q-Link 4 Send level | ||
| Touchpad X / Y CC 16 / 17 Plugin parameters Two-axis morph | ||
| L1 / R1 Notes 67 / 69 Program select Previous / next program | ||
| R3 stick click Note 72 Transport Play / Stop | ||
How do you get velocity out of digital buttons?
Set a fixed velocity per button in the bridge, and use the analogue triggers for anything that needs genuine dynamics.
A face button is a switch — there is no pressure to measure, so every hit sends the same velocity. That sounds like a limitation until you use it deliberately. Assign the kick 127, the snare 110, the closed hat 85, the ghost notes 60, and you get a programmed dynamic balance for free, with zero inconsistency between takes. For a genre built on sampled one-shots this is often better than playing velocity in badly.
When you do want real dynamics, map a trigger to fire a pad with velocity derived from the trigger's travel. L2 and R2 report their full range, and the bridge lets you shape the response curve so a light pull produces a soft hit. The adaptive trigger velocity curves deep dive walks through the curve shapes and why a linear one feels wrong.
Can you use this with a standalone MPC Live or MPC One?
Not directly — standalone MPC hardware reads MIDI, not HID, so the bridge has to run on a computer and send MIDI across to the MPC.
The route that works: run the bridge on a laptop, connect the laptop to the MPC's USB MIDI port (or use a USB-to-DIN interface into the MPC's MIDI In), and send the bridge's output across. From the MPC's point of view it is receiving MIDI from a computer, which it is entirely happy with. You lose the "no computer on stage" benefit of standalone mode, so this mostly makes sense in a studio.
Troubleshooting
- Port appears but Q-Links will not learn. The port is not set to Master in Preferences → MIDI / Sync.
- Some pads fire and some do not. Note block does not match the program's Pad MIDI Notes. Open Program Edit → Pad and read them.
- Every hit is the same loudness. Expected from digital buttons. Set per-button fixed velocities, or move the part you want dynamic onto a trigger.
- Q-Link jumps when you touch a stick. A drifting stick. Widen the deadzone — drift compensation guide.
- Port resets after unplugging. MPC sometimes drops the Master setting when a device disappears. Re-set it in Preferences.
- Only three bridge presets save. Free-tier limit. Custom note blocks need the mapping editor, which is Pro — see Pro vs Free.
FAQ
Can MPC Software be controlled from a PS5 or Xbox gamepad?
Yes. MPC Software accepts generic MIDI input for pads, Q-Links and transport, so once Universal Controller MIDI publishes the gamepad as a virtual MIDI port it behaves like any third-party controller.
Does this work in MPC Beats, the free version?
MPC Beats accepts external MIDI input and pad triggering the same way the paid MPC Software does. Some advanced features are gated in Beats, but the generic MIDI input path used here is not one of them.
What MIDI note does each MPC pad respond to?
It is set per pad and per program, visible and editable in Program Edit under the Pad tab. Read the value there rather than assuming a standard — different factory programs use different note assignments.
Can I use a gamepad with an MPC Live or MPC One hardware unit?
Only through a computer. Standalone MPC hardware accepts MIDI over USB host and 5-pin DIN, but it will not read a gamepad HID stream directly. Run the bridge on a laptop and send its MIDI out to the MPC.
Do I need Pro to set this up?
The free tier covers the default notes and CCs, which is enough to MIDI Learn a few Q-Links. You need Pro for custom note assignments to match your program, per-binding velocity curves, and more than three saved presets.
Where to go next
If you are shopping between groove boxes, the Maschine 2 guide covers the same job in Native Instruments' ecosystem and the trade-offs are genuinely different. For a full genre workflow built on this exact rig, the lo-fi hip hop loop rig walks through an entire beat start to finish.
Download Universal Controller MIDI, read your pad notes in Program Edit, and set the block to match. That one step is the whole setup.