If your music lives on an iPad, the gamepad-to-MIDI question has a different answer than it does on a laptop, and the field is far smaller. MIDItrol is the app that keeps coming up, it is cheap, it supports more controllers than you would expect, and it has an integrated OSC client that most desktop tools do not. It also has one hard iOS limitation that quietly determines whether it fits your setup at all. This piece covers what it does, what it costs, where it is clearly the right pick, and the specific setups where routing through iOS adds a device for no benefit.
- MIDItrol: $4.99 on the App Store, iOS 14.5+, four controllers at once, virtual MIDI out, OSC client.
- Controllers: DualShock 4, DualSense, Xbox One, Xbox Adaptive, Xbox Elite Series 2, MFi.
- The catch: iOS does not deliver controller events to a backgrounded app. It must stay in front.
- Last feature update was version 2.1.0 in June 2021, so treat it as stable rather than evolving.
- If your DAW is on a computer, connect the pad to the computer. The iPad hop buys you nothing.
What is MIDItrol?
It is an iOS app that turns a wireless game controller into a MIDI controller, with a virtual MIDI output for other iOS apps, USB or Wi-Fi routing to a desktop machine, and an integrated OSC client.
The vendor's framing on miditrol.com is that you can "map all the buttons, triggers and joysticks from your controller to any MIDI value", connect up to four gamepads to one device, and either play iOS instruments directly or send the result over USB or Wi-Fi to desktop software. The OSC side gives you a customisable OSC address per gamepad input, which is more than most desktop gamepad tools offer at any price.
On the App Store listing, the app is 1.2 MB, requires iOS 14.5 or later, and is published by Luis Fernando Garcia Perez. It is a small, focused, independently-made tool and it does what it says.
How much does MIDItrol cost?
It is listed at $4.99 on the App Store at time of writing, with no in-app purchases indicated.
For context, that is about a twentieth of what the desktop tools in this category cost, which makes the honest recommendation easy: if you have an iPad and a controller and you are curious whether this way of working suits you, five dollars is a cheaper experiment than any desktop trial. Even if you end up on a laptop later, you will know what you want from the mapping.
Is MIDItrol still updated?
The App Store listing shows version 2.1.0 released in June 2021, so it has not had a feature update in some time, though it remains available and purchasable.
We would not call that abandoned. A small single-purpose utility that does its job can genuinely be finished, and iOS apps that stop updating usually keep working across OS versions for years. But it does mean two things worth knowing before you buy. First, controllers released after mid-2021 are not guaranteed to be explicitly handled, although iOS's own controller framework does a lot of the lifting here. Second, if you hit a bug, the realistic expectation is that it will stay.
The listing also shows a rating of 3.7 from 10 ratings, which is a small enough sample that it tells you very little — worth saying rather than quoting as if it were a verdict.
Can MIDItrol run in the background?
No — the developer has stated there is no way to receive game controller events while the app is backgrounded, which is an iOS restriction rather than an app limitation.
This is the single most consequential fact in this article, so it is worth spelling out what it means in practice:
- You cannot have MIDItrol feeding a different iOS DAW while that DAW is on screen. The controller app must be the visible app.
- Screen lock, a notification you tap, or a phone call will stop controller input.
- Using it as a background controller for AUM, Beatmaker or Loopy is therefore not the workflow, no matter how much you want it to be.
The workable iOS patterns are: use it foregrounded on a second device (an old iPhone dedicated to the job) sending MIDI over the network to wherever the music is; or use it foregrounded on the same device as a performance surface in its own right. Our iPad AUM and Beatmaker setup guide covers the routing options, and the network MIDI guide covers the Wi-Fi hop.
iOS app versus desktop bridge: the honest comparison
They are not competing for the same job — the deciding question is where your instruments actually run.
| Consideration | MIDItrol (iOS) | Universal Controller MIDI (desktop) |
|---|---|---|
| Platform | iOS / iPadOS | macOS, Windows, Linux |
| Price | $4.99 App Store | Free tier, AUD $89 one-time Pro |
| Must stay in foreground | Yes — iOS restriction | No — runs as a background process |
| Simultaneous controllers | Up to four | Multi-controller (Pro) |
| OSC output | Yes, per-input addresses | Yes (Pro) |
| Virtual MIDI to other apps | Yes, on-device | Yes, system-wide virtual port |
| Reaches a desktop DAW | Via USB or Wi-Fi network MIDI | Directly — it is on the machine |
| Adaptive trigger haptics | Not listed | Yes (Pro) |
| Last feature update | June 2021 | Actively developed |
| Best for | Instruments running on the iPad | Instruments running on a computer |
MIDItrol details per its App Store listing and miditrol.com, as listed at time of writing. Trademarks belong to their respective owners.
When is the iOS route clearly better?
When the instruments are on the iPad, because then the controller, the app and the synth are all on one device and nothing crosses a network.
The setups where we would recommend it without hesitation:
- An iPad-only rig. AUM or Loopy as the host, hardware-free, and a controller instead of tapping glass. Five dollars is the right price for that.
- Travel. An iPad and a pad in a backpack is a smaller kit than a laptop and a pad, and it has better battery life.
- OSC experiments. Per-input OSC addresses out of the box is genuinely useful for driving visuals or a Pure Data patch. See OSC versus MIDI.
- A dedicated second device. An old iPhone running MIDItrol foregrounded as a permanent controller relay is a legitimate, cheap piece of infrastructure.
- Accessibility work. The Xbox Adaptive Controller is on the supported list, which matters. Related: one-handed production.
Which controllers work with iOS for MIDI?
DualShock 4, DualSense, Xbox One, Xbox Adaptive, Xbox Elite Series 2 and MFi controllers — all paired through the iOS Bluetooth settings before any app can read them.
Because iOS owns pairing, the troubleshooting path is short and does not involve the app at all: if the pad does not show as connected in Settings, nothing else matters. Note that iOS's controller support has expanded over the years, so a pad not named in an app's 2021 feature list may still work if the system recognises it — the app sees what the system hands it.
Relevant reading: MFi and Bluetooth controllers on iOS, the Backbone One as a MIDI controller, and the Android equivalent with the Kishi V2.
What does the desktop route look like instead?
The controller connects directly to the machine running the DAW, and a bridge publishes a system-wide virtual MIDI port that every application can open.
The practical differences that matter day to day are the background behaviour and the reach. A desktop bridge keeps running while your DAW is in front, which removes the entire class of problem that the foreground restriction creates on iOS. And because it publishes a real system port, the same controller can drive your DAW and your VJ software and a hardware synth at the same time — see routing one controller to multiple hosts.
If you are coming from iOS and want the equivalent of MIDItrol's OSC feature on the desktop, that exists too: the Open Stage Control hybrid setup and the Reaper OSC guide both cover it.
What is the cheapest way to find out whether this suits you?
Buy the iOS app if you own an iPad, or install a free desktop tier if you own a laptop — both answer the same question for under the price of a cable.
The question being answered is not "which product is best". It is "does a gamepad belong in my workflow at all", and that is a personal answer nobody can give you from a feature table. Some people pick one up and never put it down, because a trigger under a finger is a better expression controller than a mouse will ever be. Others find the spring-loaded sticks fight them and go back to a knob box within a week. Both are valid and neither is predictable in advance.
Spend five dollars or ten minutes, map one trigger to a filter, and play for twenty minutes. You will know. If the answer is yes, then start comparing products properly — the full field guide is the place for that.
Why is the iOS field so much smaller than the desktop one?
Because iOS gives app developers a narrower, more controlled surface — which produces fewer apps, but also fewer broken ones.
Three structural reasons, all of which cut both ways:
- No raw HID access. Apps read controllers through the system framework, so nobody can parse a DualSense's raw report to get at adaptive trigger control. The upside is that every app gets consistent, well-behaved controller support for free.
- Strict background rules. The foreground requirement that limits MIDItrol limits everyone equally. It is the reason no iOS app can be a true background input daemon the way a desktop bridge can.
- A smaller paying market. Music software on iOS is priced in single-digit dollars, which supports small focused apps and not large ones. That is why the good iOS tools are five-dollar utilities rather than ninety-dollar products.
The result is a category with fewer options and less variance in quality. On desktop you have to check whether a tool is archived, whether it reads your controller properly and whether it even emits MIDI. On iOS the short list is short and the apps mostly work. If you are choosing a platform for a simple controller rig and nothing else, that is a genuine point in iOS's favour — see the MFi controller guide for what the system handles on your behalf.
How do you get iOS MIDI to a desktop machine if you do want to?
Two routes — a USB cable, or a network MIDI session over Wi-Fi — and they fail in different ways.
USB is the dependable one. The iPad or iPhone connects to the computer and appears as a MIDI device, with latency low enough to play rhythmically and no network to go wrong. The cost is that you are tethered, which removes most of the reason to use a wireless controller in the first place.
Network MIDI is the interesting one. On macOS it is built into Audio MIDI Setup as a Network session; on Windows it needs rtpMIDI, from the same developer as loopMIDI. It works well on a quiet network and badly on a busy one, and a venue's Wi-Fi is the definition of a busy network. We cover the setup and the failure modes in the network MIDI guide and rtpMIDI versus USB.
Either way, remember that you are now stacking two wireless links if the controller is also on Bluetooth: pad to phone, phone to network, network to computer. That is three hops to deliver a button press that could have travelled one.
What does an iPad-first rig actually look like?
One iPad running the host, the controller app foregrounded on a second cheap device, and MIDI travelling between them — or one iPad doing everything with the controller app as the performance surface.
The second pattern is the one people underrate. Instead of treating the controller app as a background utility feeding a DAW, treat it as the instrument: foreground it, map its outputs to an on-device synth over virtual MIDI, and play. The foreground restriction stops being a limitation when the app you need in front is the one you are playing.
For the first pattern, an old iPhone that no longer holds a charge well is a perfectly good permanent controller relay, because it can stay plugged in. Our AUM and Beatmaker setup covers the host side, the battery-only busking rig covers running the whole thing without mains power, and the GarageBand iPad guide covers the simplest possible version.
FAQ
What is MIDItrol?
MIDItrol is an iOS app by Luis Fernando Garcia Perez that turns a wireless game controller into a MIDI controller, with a virtual MIDI output for other iOS apps, USB or Wi-Fi routing to a desktop machine, and an integrated OSC client.
How much does MIDItrol cost?
It is listed at $4.99 on the App Store at time of writing, with no in-app purchases indicated and a minimum requirement of iOS 14.5 or later.
Is MIDItrol still updated?
Its App Store listing shows version 2.1.0 released in June 2021, so it has not had a feature update in some time, though it remains available and purchasable.
Can MIDItrol run in the background?
No — the developer has stated there is no way to receive game controller events while the app is in the background, which is an iOS restriction rather than an app limitation, so the app must stay in the foreground.
Should I use an iOS gamepad MIDI app or a desktop bridge?
Use the iOS app if the instruments are on the iPad or iPhone, and use a desktop bridge if your DAW runs on a computer, because relaying a controller through a phone to reach a laptop adds a device, a wireless hop and a foreground requirement for no benefit.
Which controllers work with iOS for MIDI?
MIDItrol lists DualShock 4, DualSense, Xbox One, Xbox Adaptive, Xbox Elite Series 2 and MFi controllers, all paired through the iOS Bluetooth settings before any app can read them.
The short version
MIDItrol is a good five-dollar app and the sensible pick for an iPad-based rig, with a real OSC implementation and support for more controllers than most desktop tools. Its foreground requirement is an iOS rule, not a flaw, but it does decide the question for anyone hoping to run it behind another iOS DAW.
If your instruments run on a computer, skip the relay. Download Universal Controller MIDI free on the machine your DAW is on — one controller, one virtual port and three saved presets on the free tier, AUD $89 one-time for Pro with the mapping editor, multi-controller routing, MPE and OSC. Next: every gamepad-to-MIDI tool compared.