How to Use Your iPhone as a MIDI Controller in Studio One

What you need

• An iPhone — the controller. Nothing else to buy.
• NueCtrl — free on the App Store. A one-time Pro in-app purchase adds Max Mode (up to 500 Hz motion capture), unlimited faders, per-fader sensitivity and unlimited presets.
• A Mac or Windows PC running Studio One. External Devices and Control Link are part of the core program; a couple of the targets in Part 3 — Mix Engine FX in particular — belong to the Professional edition only.
• One connection route — Bluetooth, the same Wi-Fi network as your computer, or a Lightning / USB-C cable.

Part 1 — Connect your iPhone

This part is the same for every DAW, because it happens at the operating-system level before Studio One is involved. Pick one of the three routes below. If you want the full walkthrough with screenshots of each dialog, see the MIDI connection setup guide.

Option A — Bluetooth LE MIDI

The fastest route, and the only one that needs no cable and no shared network. NueCtrl advertises itself over Bluetooth LE when it launches.

1. On your iPhone, open Settings → Bluetooth and make sure Bluetooth is on.
2. Launch NueCtrl and go to Settings → Connection → Bluetooth MIDI, then tap Advertise so the phone is visible.
3. On your Mac, open Audio MIDI Setup (Applications → Utilities), choose Window → Show MIDI Studio, and click the Bluetooth icon.
4. Find NueCtrl BLE in the device list and click Connect. NueCtrl's status indicator will read Connected.

Option B — Wi-Fi (Network / RTP-MIDI)

Lower latency than Bluetooth, still wireless. Roughly 5 ms in practice.

1. Put the iPhone and the computer on the same Wi-Fi network — 5 GHz if you have the choice.
2. macOS: Network MIDI is built in. Open Audio MIDI Setup → Window → Show MIDI Studio, double-click the Network icon, click + under My Sessions and tick Enabled. Select NueCtrl in the Directory panel and click Connect.
3. Windows: there is no built-in Network MIDI. Install rtpMIDI (the free RTP-MIDI driver from Tobias Erichsen), create a session in it, and connect to NueCtrl from its directory list.
4. In Studio One, the input will appear under the session name (for example Session 1), not under the phone's name.

Option C — USB

The lowest latency and the most reliable route — around 2 ms — and the right choice for a take you intend to keep.

1. Connect the iPhone to the Mac with a Lightning or USB-C cable.
2. First time only: in Audio MIDI Setup, choose Window → Show Audio Devices, select your iPhone and click Enable.
3. NueCtrl detects the cable and switches to USB MIDI automatically. The port appears as NueCtrl.

Part 2 — Studio One setup

Studio One will not use a MIDI port until you have told it what the port is for. That happens in one dialog, and the dialog contains the two fields people most often get wrong. Get them right and the rest of Studio One's mapping system is genuinely the fastest of any major DAW.

Step 1 — Add the device under External Devices

1. Open Studio One's settings. On macOS this is Studio One → Settings; on Windows it is Options → Settings. Before Studio One 6 the same pane was called Preferences — that rename is why older tutorials send you looking for a menu item that no longer exists.
2. Go to External Devices and click Add…. Studio One opens a browser of manufacturers and device types.
3. Choose New Control Surface. This is the entry that makes the port visible to Control Link, and Control Link is what performs parameter assignment.
4. Set Receive From to the port carrying NueCtrl: NueCtrl BLE for Bluetooth, the session name for Wi-Fi, or NueCtrl for USB.
5. Give the device a name you will recognise — NueCtrl is fine — and confirm. It now appears in the External Devices list.
6. Optional but often worth it: repeat the process and add the same port a second time as a New Keyboard, so the CC and note stream can also be recorded straight into an instrument track.

Step 2 — Assign a parameter with Control Link

Control Link is Studio One's mapping system, and it lives in the strip at the top left of the arrange window. The strip has two halves: the incoming hardware control on one side, and the target parameter in Studio One on the other. Assignment is the act of joining them.

1. With the device connected, move your iPhone so NueCtrl sends its CC. The incoming controller registers on the hardware side of the Control Link strip.
2. Click the parameter you want to control in Studio One — a Macro Control knob, a send level, a filter cutoff inside a plugin. It appears on the target side of the strip.
3. Join the two sides using the link control between them. The assignment is live immediately; there is no separate mapping mode to leave.
4. Decide whether the assignment should be a Focus or a Global one — the two buttons for this sit in the Control Link strip. The next step explains the difference, because it changes what the assignment actually does.

Step 3 — Focus or Global: the decision that defines Studio One mapping

This is Studio One's signature idea, and it is the thing most controller guides skate over. A Focus assignment is attached to whichever plugin currently has focus. Assign your phone to a filter cutoff in one synth as a Focus mapping, and the same phone movement will reach the equivalent control in the next plugin you bring to the front. One assignment, every plugin — you never map the same gesture twice.

A Global assignment ignores focus entirely and stays welded to one specific target. That is what you want for anything that must keep working while you are looking at something else: a send level feeding a reverb bus, a parameter on a master-bus effect, a volume fader you are riding.

The practical rule: use Focus for a general-purpose "sweep whatever I am working on" control, and Global for a fixed destination you want to reach without changing what is on screen. Most people end up with one of each, and it is worth deliberately choosing rather than accepting whichever mode the strip happened to be in.

Step 4 — Record the movement as automation

An assigned parameter behaves exactly like one you moved with the mouse, which means Studio One will record it. Set the automation mode for the track or plugin to Touch or Latch, start recording, and perform the movement while the part plays. Touch writes only while you are moving and returns to the previous value afterwards; Latch keeps writing from the moment you first move until you stop the transport. Studio One draws an automation envelope you can then reshape, trim or copy elsewhere. Read and Off write nothing at all, which is worth remembering before you perform a take you cannot repeat.

Part 3 — What to map in Studio One

NueCtrl turns iPhone motion into continuous MIDI CC, so it pays off on parameters that are meant to move rather than on switches. Studio One has a few targets that suit a moving hand unusually well.

Macro Controls

The highest-leverage target in the program. Every channel and every FX Chain carries a Macro Controls panel of knobs and buttons, and a single Macro knob can be wired to several plugin parameters at once, each with its own range. Set that up first, then Control Link your phone to the one knob. A single tilt now moves filter cutoff, reverb amount and drive together while you manage exactly one assignment and one automation envelope. If you have used Ableton's Macros, this is the direct equivalent, and it is the first thing to build.

FX Chains

An FX Chain bundles several effects into one reusable unit, and it carries its own macro panel. Build the chain you actually use — filter into saturation into delay, say — expose the two or three parameters that matter on the macro panel, and drive the whole assembly with one movement. The chain travels between songs with the assignment layout intact, so the setup cost is paid once.

Mai Tai and Presence XT continuous parameters

The bundled instruments give you plenty of sweepable ground without buying anything. Mai Tai's filter cutoff and its modulation-matrix depths respond well to a slow hand, and the matrix depths in particular are where motion control stops sounding like an effect and starts sounding like playing. In Presence XT, filter cutoff and sample start are the two that reward a continuous controller most.

Send levels to a bus

Riding a send into a reverb or delay bus is a classic mix move that rarely sounds right when it is drawn with a mouse, because it is fundamentally a performance. Assign NueCtrl to the send level as a Global mapping — you want it to keep working while you are looking at a plugin window — and push the vocal into the tail at the end of each phrase, then pull it back for the next one.

Mix Engine FX and Console Shaper drive

In editions that include Mix Engine FX, the bundled Console Shaper adds a drive-style colour across the bus rather than in a single insert. It is a subtle, wide control, which makes it an unusually good match for a slow hand movement: a few degrees of tilt across a chorus is enough to hear without ever reading as an obvious automation move.

CC1 and CC11 into orchestral and sampled instruments

If you run orchestral or sampled libraries in Studio One, send NueCtrl's output to CC1 (modulation) and CC11 (expression) and drive the library's own dynamics and expression layers directly. No Control Link assignment is required here at all — the instrument already listens to those controllers, so the port you added as a Keyboard is doing the work. Sustained string and brass lines live or die on the shape of the CC11 curve, and this is where a moving hand beats a mouse most plainly.

Troubleshooting

• The device is in the External Devices list but nothing responds. Receive From was left blank when the device was created. Studio One allows this and gives no warning: the device exists and is deaf. Reopen it and select the port carrying NueCtrl. This is the single most common cause.
• Control Link ignores the phone entirely. The port was probably added as a New Keyboard rather than a New Control Surface. A Keyboard feeds note and CC data into tracks but is not what Control Link assigns from. Add the same port again as a Control Surface — you can keep both entries.
• A Focus assignment appears to have stopped working. It has not; the plugin you intended to control simply does not have focus, so the assignment is pointing somewhere else. Click the plugin window to give it focus and try again. If you want that control to keep working no matter what is on screen, recreate the assignment as Global instead.
• The port is not offered in the Receive From list. Studio One enumerates MIDI ports at launch. Finish the connection at the operating-system level first — pair over Bluetooth or connect the Network MIDI session in Audio MIDI Setup — then restart Studio One so the port is there to be chosen.
• Movement is audible but late. Bluetooth runs around 10-15 ms, Wi-Fi around 5 ms and USB around 2 ms, so change route before you blame anything inside Studio One. If you are already on USB, reduce the audio device's block size in the audio setup section of Settings — a large block size adds delay on top of whatever the MIDI route costs.
• On Windows there is no USB route. Getting MIDI off an iPhone over USB depends on macOS exposing the phone in Audio MIDI Setup, so Windows users should use Wi-Fi with rtpMIDI for the low-latency path. It is the dependable wireless route on Windows in any case.
• The performance played back but no envelope was written. The automation mode was on Read or Off. Only Touch and Latch write while you perform. Set the mode before the take, not after.

FAQ