iPhone MIDI over USB:
The Step Everyone Misses
You plugged your iPhone into your Mac. The phone is charging. Your DAW shows no new MIDI input, and your iPhone app shows no devices. Nothing is broken.
macOS finds the iPhone immediately — but it leaves the phone's MIDI ports switched off until you turn them on by hand. There is no prompt, and no error.
Why Nothing Shows Up
When you connect an iOS device over USB, macOS registers it in MIDI Studio in a disabled state. Until you enable it, the MIDI endpoints genuinely do not exist — not to Logic, not to Ableton, and not to the app running on the phone.
That last part is what makes this so confusing to diagnose. There is no half-connected state to notice, no greyed-out entry in your app's device list, no permission prompt to decline. From inside an iPhone app, a Mac that hasn't been enabled is indistinguishable from no Mac at all. Every symptom points at the app, and the app has no way to see the problem or tell you about it.
This is also why swapping apps never helps. Any iPhone MIDI app hits the same wall, because the missing piece is on the Mac.
The Fix
- 1
Connect the iPhone to the Mac with a cable that carries data, and unlock the phone. Tap Trust if you are asked.
- 2
On the Mac, open Audio MIDI Setup, in
/Applications/Utilities. - 3
Choose Window → Show MIDI Studio (⌘2). Your iPhone appears here, greyed out.
- 4
Select it and click Enable in the toolbar. The icon becomes active and the MIDI ports come into existence.
macOS remembers this per device, so it is a one-time step for each phone. You do not repeat it every time you plug in.
If It Still Doesn't Appear
Check the cable first
A charge-only cable powers the phone and carries no data, which looks exactly like a software fault. This is the single most common cause after the Enable step. Swap the cable before you investigate anything else.
Rescan on the Mac
In MIDI Studio, click Rescan MIDI — the circular arrow in the toolbar.
Skip the hub
Bus-powered hubs and docks are a frequent source of flaky enumeration. Try a port on the Mac itself.
Arm the track
Once the device exists, most DAWs still need the track armed and set to receive from it before you hear anything.
Why Bother With the Cable
Bluetooth MIDI is genuinely good and needs no setup on either end. But USB wins on the two things that matter in a studio: it has the lowest and most consistent latency of any transport, and it charges the phone while you play — which matters more than it sounds when the screen is on and the sensors are running.
| Transport | Added latency | Setup |
|---|---|---|
| USB | ~1–2 ms | Enable once in Audio MIDI Setup |
| Bluetooth LE | ~10–20 ms | Pair in the app |
What Changed in Mobile MIDI 1.1.0
An app can't detect the missing Enable step — so the next best thing is to say so at the moment you'd be stuck. The connection screen now explains what each transport needs when no devices are found, instead of showing an empty list. It also makes the connection itself legible: devices sit under AVAILABLE until you tap one, then move into a green CONNECTED box, with progress shown while it's working.
Bluetooth scanning now stops by itself once you're connected, which is a small change with a real effect on battery life during a session.
Network MIDI has been removed in this version. It worked, but it needed a session created and enabled on the desktop side before it did anything, and it was consistently the transport people got stuck on. Bluetooth and USB cover the same ground with less ceremony. As a result Mobile MIDI no longer requests Local Network access at all.
Turn your iPhone into a MIDI controller
Touch pads, keys, XY and faders, six-axis motion, face and hand tracking, and AirPods head movement — all mappable to MIDI, all processed on-device.