Maschine 2 — Gamepad MIDI Control for Pads and Macros

Maschine's software is the half of the product people forget you can buy and use on its own. Maschine 2 runs standalone or as a plugin with no hardware attached, and it accepts generic MIDI for the pads, the Macro Controls and the transport. That makes a gamepad a legitimate — and very cheap — way into the Maschine workflow if you do not own, or do not want to carry, a Maschine MK3. This guide sets up a Maschine gamepad MIDI controller rig using Universal Controller MIDI to publish a DualSense, Xbox or 8BitDo pad as a virtual MIDI device.

Why use a gamepad with Maschine at all?

Three real reasons, none of them "because it is funny".

One — portability. A Maschine MK3 is a desk instrument. A gamepad fits in a jacket pocket and runs off the laptop's USB port. If you write on trains, in hotels, or on a couch, that difference decides whether you open the session at all.

Two — the triggers. Maschine's hardware has touch-sensitive knobs but no analogue pedal-style control. A gamepad has two, and they are the single best thing on the device for riding a filter or a send in real time. Pair them with Maschine's eight Macro Controls and you get hands-on modulation the hardware does not offer in that shape.

Three — eight pads is often enough. Sixteen pads is great for a finished kit, but most beats are built from four to eight elements. Four face buttons plus the d-pad gives you exactly that, in a layout your thumbs already know. We went deep on this in the finger drumming workflow guide.

What you need

• Maschine 2 — standalone or plugin, Maschine Essentials upward
• Universal Controller MIDI — download for macOS or Windows
• A supported gamepad — DualSense, DualShock 4, Xbox Series, Switch Pro, 8BitDo
• macOS: IAC Driver online. Windows: nothing extra, the bridge ships its own port

How do you get a gamepad into Maschine's MIDI input?

Publish the virtual port first, then enable it under Preferences → MIDI → Input in Maschine standalone — in the plugin version the host DAW routes MIDI instead.

1. Virtual port

On macOS: Cmd-Space, Audio MIDI Setup, Window → Show MIDI Studio, double-click IAC Driver, tick Device is online. On Windows the bridge installs a kernel-level virtual port during setup. The virtual port explainer covers what differs between the two.

2. Enable it in Maschine

Launch the bridge first, then Maschine. In the standalone app, open Preferences → MIDI. There are separate Input and Output lists; tick UCM Bridge on the Input side only. Maschine rescans MIDI devices when you open this page, so if the port is missing, close and reopen Preferences before you assume anything is broken.

If you are running Maschine as a plugin inside a DAW, skip this entirely. The host owns MIDI routing — create a MIDI track, set its input to the bridge port, set its output to the Maschine plugin instance, and arm it.

3. Turn on Group MIDI input

Select a Group in the Maschine arranger, open the Channel page, and switch to the MIDI tab. Enable Input, set the source to the bridge port, and set the MIDI channel. This is the step that actually lets external notes hit the pads — enabling the port in Preferences alone does nothing until a Group is listening.

Which notes hit which pads?

Maschine maps sixteen consecutive notes upward from whatever root note you set in the Group's MIDI tab — so set the root to match the lowest note your bridge preset sends and everything lines up.

This is the single most-misunderstood part of controlling Maschine over generic MIDI. There is no fixed universal pad note range you need to memorise; there is a root note you choose, and sixteen notes from there. The bridge's default preset sends notes 60, 62, 64, 65 for the face buttons and 78–81 for the d-pad, which is a musical layout rather than a contiguous block.

For pad work you want a contiguous block instead. In the bridge's mapping editor, set the eight trigger buttons to consecutive notes — 36, 37, 38, 39, 40, 41, 42, 43 is the obvious choice because note 36 is the conventional kick drum position in most drum maps. Then set Maschine's root note to 36 and your face buttons land on pads 1–4, your d-pad on pads 5–8. Note that custom bindings like this require the mapping editor, which is a Pro feature — the Pro vs Free page is clear about where that line sits.

How do you bind the sticks and triggers to Macro Controls?

Build the Macro page first — drag the parameters you care about onto Macro slots — then bind each gamepad CC to a Macro through the Channel page MIDI tab.

Maschine's Macro Controls are the right destination for everything analogue on the pad. Eight slots, available at the Group and Sound level, and each one can host any parameter from anywhere in that Group's chain. The workflow:

1. Select the Group, open the Macro page on the Channel view.
2. Right-click a parameter anywhere in the Group — a filter cutoff, a reverb amount, a sample start point — and assign it to a Macro slot.
3. Name the Macro so it reads sensibly on screen.
4. In the Channel page MIDI tab, bind incoming CC numbers to Macro slots 1 through 8.

Then: L2 and R2 on Macros 1 and 2 (parked values — filter, drive), left stick on Macros 3 and 4 (gestures — pitch, stutter depth), right stick on Macros 5 and 6 (sends), touchpad on Macros 7 and 8 (two-axis morph). The touchpad XY guide covers calibrating that last pair properly.

Default mapping table for Maschine 2

A working layout. The note column assumes you have remapped the buttons to a contiguous block from 36 and set Maschine's root note to match.

Working Maschine 2 layout

Control	MIDI message	Target
Cross / A → Note 36 → Pad 1 Kick
Circle / B → Note 37 → Pad 2 Snare
Square / X → Note 38 → Pad 3 Closed hat
Triangle / Y → Note 39 → Pad 4 Open hat
D-pad up → Note 40 → Pad 5 Clap
D-pad right → Note 41 → Pad 6 Rim / perc
D-pad down → Note 42 → Pad 7 Tom
D-pad left → Note 43 → Pad 8 Crash / FX hit
L2 trigger → CC 1 → Macro 1 Group filter cutoff
R2 trigger → CC 2 → Macro 2 Drive / saturation
Left stick X → CC 3 → Macro 3 Sample start / pitch
Left stick Y → CC 4 → Macro 4 Beat repeat depth
Right stick X → CC 5 → Macro 5 Delay send
Right stick Y → CC 6 → Macro 6 Reverb send
Touchpad X / Y → CC 16 / 17 → Macros 7 / 8 Two-axis FX morph
L1 / R1 → Notes 67 / 69 → Group select Previous / next Group

Does velocity work from a gamepad's face buttons?

Face buttons are digital, so they send a fixed velocity — but the analogue triggers are not, and that is where expressive velocity comes from.

A DualSense face button is a simple on-off switch; there is no pressure reading to turn into velocity. What you can do is set a fixed velocity per button in the bridge's mapping editor, which is genuinely useful: put the kick at 127, the hats at 95, the ghost snare at 60, and you get a programmed dynamic feel without any finger control at all.

For real dynamic playing, use the triggers. L2 and R2 report their full travel, so a trigger pull can produce a note with velocity derived from how hard you pulled. The adaptive trigger velocity curves deep dive goes through the response shapes in detail — it is the difference between a trigger that feels like a switch and one that feels like a drum pad.

Troubleshooting

• Port missing in Preferences → MIDI. Maschine scanned before the bridge was running. Close and reopen the Preferences page, or restart Maschine.
• Notes arrive but no pads fire. Group MIDI input is off. Channel page → MIDI tab → enable Input.
• Wrong pads trigger. Root note mismatch. Set Maschine's root to the lowest note in your contiguous block.
• Macro moves but the parameter does not. The Macro slot is empty — assigning a CC to a Macro does nothing until a parameter is dragged into that slot.
• Audible stepping on slow filter sweeps. 7-bit CC resolution. Enable smoothing in the bridge, or use a shorter parameter range so 128 steps cover less ground.
• Plugin version ignores the controller. In plugin mode the DAW routes MIDI; create a MIDI track pointed at the Maschine instance and arm it.

FAQ

Can Maschine software be controlled by a PS5 or Xbox gamepad?

Yes, through a MIDI bridge. Maschine 2 accepts generic MIDI input for pads, Macro Controls and transport, so once Universal Controller MIDI publishes the gamepad as a virtual MIDI port, Maschine treats it like any third-party controller.

Do I need Maschine hardware for this to work?

No. Maschine 2 software runs standalone or as a plugin without the hardware attached, and the MIDI input path used here does not depend on a Maschine controller being present.

Which notes trigger the pads?

That depends on the root note you set in the Group Channel page MIDI tab. Maschine maps sixteen consecutive notes upward from that root to pads 1 to 16, so set the root to match the lowest note your bridge preset sends and the rest line up automatically.

Should I use the standalone app or the plugin?

Standalone is simpler for a gamepad because Maschine owns its own MIDI preferences. In the plugin version, the host DAW controls MIDI routing and you send the bridge port to the Maschine track instead.

Can the triggers control Macro knobs smoothly?

Yes. The analogue triggers send a continuous CC over their full travel, which maps cleanly onto a Macro. Standard MIDI CC is 7-bit so you get 128 steps — enable smoothing in the bridge if you can hear stepping on slow sweeps.

Where to go next

Once the pads and Macros are wired, the obvious extension is the rest of the Native Instruments ecosystem — the same CCs will drive Massive X macros or a Reaktor Blocks rack without any new setup. If you are comparing groove boxes rather than committed to Maschine, the MPC Software guide covers the same workflow in Akai's world.

Download Universal Controller MIDI, point a Group at the bridge port, and make a beat on the couch.