Gamepad MIDI iPad AUM + BeatMaker 3 — Full Setup

The gamepad MIDI iPad AUM workflow turns iPadOS into a real performance rig for the price of a controller you probably already own. AUM 1.4 is the mixer, BeatMaker 3.5 handles the pads, a PS5 DualSense and a HID-to-MIDI bridge do the tactile work. Behold: 16 buttons, two analog triggers, two sticks, a touchpad, and motion data — over Bluetooth or USB-C. This is the end-to-end setup — pairing, bridging, routing, mapping, latency tuning — for both apps, with the gotchas that cost most people an evening of forum scrolling.

AUM on iPadOS is the most flexible host you can carry in a backpack

AUM hosts unlimited AUv3 plugins, routes MIDI freely, and runs a sample-accurate clock on a glass slab you take to the kitchen. BeatMaker 3 is its drum-machine cousin — 64 pads per scene and a sequencer Elektron users would actually use.

Touch is great for transport and terrible for fast performance gestures. The DualSense gives you 16 buttons, 2 sticks, 2 analog triggers, a touchpad, and motion sensors — more controllable surface than most $300 controllers, lighter, and eight hours on a charge. The catch: iPadOS does not send HID gamepad events to Core MIDI. You need a bridge.

Pick the host before you map a single button — they're not interchangeable

AUM is the mixer/host. BeatMaker 3 is the MPC. GarageBand is the friendliest and the most locked-down. Choose one, then commit.

Three ways to bridge — pick by what you already own

Same outcome, different gear:

• Mac + Network Session MIDI — most reliable, ~3 ms over Ethernet, ~6–9 ms over Wi-Fi. Run Universal Controller MIDI on the Mac, expose its port over the network, join from the iPad.
• Direct iPad HID-to-MIDI app — newer iPadOS apps read the Game Controller framework and emit Core MIDI internally. No Mac needed. Latency is the lowest (under 4 ms) because there is no network hop.
• USB-C dongle into iPad — plug a Mac-style MIDI interface into the iPad, run the bridge on another machine, send hard-wired MIDI in. Overkill for most, but the most jitter-resistant option for live shows.

What you'll need

• iPad on iPadOS 16 or later — earlier versions have flaky Bluetooth HID handling.
• AUM 1.4+ or BeatMaker 3 3.5+ (both are on the App Store).
• DualSense, DualSense Edge, or Xbox Wireless Controller. The Xbox Series controller needs Bluetooth firmware 5.x+ for HID gamepad mode.
• Universal Controller MIDI on a Mac (optional but recommended for the preset library).
• USB-C to USB-C cable if you want wired latency. Most iPads from 2018 onward have a USB-C port that supports HID hosts.

Pairing a DualSense to iPadOS — 30 seconds, then the catch

Hold PS + Create on a DualSense (or Xbox + sync on an Xbox pad) until the light bar pulses. On the iPad, open Settings → Bluetooth and tap the controller. iPadOS 16+ shows it as DualSense Wireless Controller.

Any app using the Game Controller framework can now read it — every iOS game, but not AUM or BeatMaker 3. You still need the bridge.

Wire it. Bluetooth jitter ruins finger drumming

Bluetooth jitter on iPadOS averages 5–9 ms and spikes to 20 ms when the Wi-Fi radio is busy. Wired USB-C is a flat 2–4 ms. Studio noodling is fine over Bluetooth — anything quantised live, wire it.

Route 1: Mac bridge over Network Session MIDI — the bulletproof option

Run Universal Controller MIDI on your Mac. The DualSense connects to either the Mac or the iPad — the bridge picks it up via the Game Controller framework. Open Audio MIDI Setup → Window → Show MIDI Studio → Network. Create a session called UCMIDI-Net, tick Anyone under Who may connect. On the iPad: AUM → ⚙ → MIDI Control → Connections → Network Session, join UCMIDI-Net.

In AUM, tap any channel's MIDI input slot, pick Network Session 1 — that is your gamepad. Drop in a synth (Ripplemaker, Model 15, Synth One) and point its MIDI input at the same port. Buttons fire notes, triggers send CC 1 and CC 2, sticks send CC 3–6.

Network MIDI latency budget

Same router, end-to-end is 6–9 ms. Plug both devices into Ethernet (yes, an iPad Pro takes a USB-C Ethernet adapter) and it drops to 3 ms. Seeing 15 ms+? Your Wi-Fi is the bottleneck — pin to 5 GHz or run a hotspot from the Mac.

Route 2: iPad-only — fewer hops, lower latency

iPadOS apps now read the Game Controller framework and emit Core MIDI directly. Pair the controller, open the bridge app, enable its virtual destination, point AUM at it. No Mac, no network session, no router. Latency drops under 4 ms. The virtual MIDI port explainer covers the plumbing if you want it.

The catch: iPad-only bridges expose fewer presets and most don't ship adaptive trigger output (desktop Pro feature). Want haptic feedback driven by incoming MIDI? Run the Mac bridge. Just notes and CCs? iPad-native is faster to set up.

AUM 1.4 mapping template — what I actually route live

This is the mapping I run on stage. Channels 1–3 are a drum rack (Ripple), a bass synth (Model 15), and a pad (Zeeon). Channel 4 is granular processing (KRFT) on a return.

Behold the .aumpreset excerpt the bridge ships — drop it into AUM via Tools → Import Preset and the routing above lights up instantly. It's XML-flavoured plist under the hood — the readable bits are the MIDI input slot and the per-plugin learn map.

<aumpreset version="1.4">
  <midi-input name="Network Session 1" channel="omni"/>
  <channel id="1" plugin="Ripplemaker">
    <learn note="36" param="pad1.trig"/>
    <learn note="38" param="pad2.trig"/>
    <learn note="42" param="pad3.trig"/>
    <learn note="46" param="pad4.trig"/>
  </channel>
  <channel id="2" plugin="Model 15">
    <learn cc="1" param="filter.cutoff" curve="exp"/>
  </channel>
  <channel id="4" plugin="KRFT" returns="A">
    <learn cc="3" param="grain.size"/>
    <learn cc="4" param="grain.position"/>
  </channel>
</aumpreset>

BeatMaker 3 — an MPC on glass that finally has hardware buttons

BeatMaker 3.5 is the obvious pairing: 64 pads per scene, per-pad effects, a sequencer that holds up. Full MIDI implementation in the Intua BeatMaker 3 docs. Open Setup → MIDI → Input Ports, enable the bridge port. The 16 face buttons + d-pad map to the first 16 pads. Triggers ride pad pressure. Sticks drive FX-rack macros.

Trigger-as-pad-velocity — the killer feature

BM3 has velocity-sensitive pads. In the bridge UI, Settings → Output, switch face buttons from fixed velocity 100 to analog velocity from trigger. Now Cross + L2 at 60% sends note 60 at velocity 76. It feels like real pads, plus one continuous controller per finger.

Sequencer step entry without looking

In BM3's step sequencer, the face buttons are steps 1–4 when MIDI Learn is in step-edit mode. Hold L1 to shift to steps 5–8, R1 for 9–12, both for 13–16. Faster than tapping the screen once muscle memory kicks in, and it works eyes-up — which matters if you're also driving lights, like the DMX bridge setup covers.

Latency tuning for gamepad MIDI iPad AUM rigs and Bluetooth gotchas

• Disable Bluetooth audio when using Bluetooth controller. iPadOS time-slices the 2.4 GHz radio between A2DP audio and HID controller. With both on you will see 15–25 ms jitter spikes.
• Force 5 GHz Wi-Fi. If your router auto-bands to 2.4 GHz, network MIDI sessions slow down. Pin the iPad and Mac to a 5 GHz SSID.
• Lower AUM's buffer to 128 samples. Default is 256, which adds ~5 ms on top of MIDI latency. iPad Pro M-series handle 128 with most plugins.
• Quit Logic Remote and GarageBand. They grab Core MIDI input ports and starve other apps. The GarageBand iPad guide covers that workflow separately.
• Check for double notes. If you joined the network session in both AUM and the system MIDI Studio, AUM receives every event twice. Pick one.

Adaptive trigger feedback — feel the kick punch back

The Pro tier sends MIDI back to the controller and converts it to adaptive-trigger resistance or haptic pulses. Route AUM's master side-chain envelope to a virtual MIDI output, point it at the bridge's haptic input, and L2 fights your finger every time the kick hits. Same feature as the adaptive triggers feedback post — works the same on iPad over network MIDI as it does on desktop.

FAQ

Does AUM 1.4 support gamepad MIDI on iPad natively?

No. AUM reads Core MIDI, not HID gamepad events. You need a bridge app or a Mac running Universal Controller MIDI to translate DualSense input into MIDI before AUM can see it. Once the virtual port is exposed, AUM treats the gamepad like any other MIDI controller.

Can I run BeatMaker 3 from a DualSense without a Mac?

Yes. iPad-native HID-to-MIDI bridges read the Game Controller framework directly and emit Core MIDI on-device, which BeatMaker 3.5 picks up under Setup → MIDI → Input Ports. Latency drops to under 4 ms with no network hop.

Does an Xbox controller work for gamepad MIDI on iPad?

Yes — Xbox Wireless Controllers on Bluetooth firmware 5.x or later pair to iPadOS 16+ as HID gamepads, same as the DualSense. You lose the touchpad and adaptive triggers, but the 16 buttons and two sticks still route through any HID-to-MIDI bridge.

What is the lowest-latency gamepad MIDI iPad AUM setup?

Wired USB-C controller into an iPad Pro running an iPad-native HID-to-MIDI bridge, AUM buffer at 128 samples. End-to-end is under 6 ms. Network Session MIDI from a Mac is the second-best option at 6–9 ms over a quiet 5 GHz Wi-Fi link.

Where do I get the AUM and BeatMaker 3 templates?

Inside Universal Controller MIDI under Presets → iPad → AUM and Presets → iPad → BeatMaker 3. The .aumpreset and .bmproject files load directly in each app and match the mapping table above.

The verdict: a 90-second pre-session check saves the gig

Open AUM, hit the test note on a synth, press Cross. Hear the note within a single frame of the click? You're good. If not, kill Bluetooth audio, disable unused MIDI ports, reconnect the network session. Five minutes once means the controller behaves identically every time you pick it up.

Grab Universal Controller MIDI, pair the gamepad, and your iPad becomes a portable studio with proper tactile control.