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

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 Windows PC or Mac running FL Studio. Controller linking is part of the program itself, so every edition can do it — Fruity, Producer, Signature and All Plugins all expose the same MIDI Settings page and the same right-click Link to controller command.
• 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 FL Studio 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 FL Studio, 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.

That last point matters more here than in most guides, because FL Studio's user base leans heavily Windows: if you are on a PC there is no USB option to look for, and the Wi-Fi route with rtpMIDI is your low-latency path — around 5 ms, close enough to a cable that the difference will not decide a take.

Part 2 — FL Studio setup

FL Studio arrives with every MIDI input switched off, so a phone that is perfectly connected at the OS level can still look completely dead inside the program. Two things have to happen: the port has to be enabled, and the parameter you want has to be linked.

Step 1 — Enable the input

1. Open Options → MIDI Settings. The F10 shortcut opens the same page directly and is the fastest way in.
2. Look at the Input list. The port carrying NueCtrl will be named NueCtrl BLE over Bluetooth, the session name over Wi-Fi, or NueCtrl over USB.
3. Click that row to select it.
4. Click Enable beneath the list. The entry is then marked as active.
5. Optional: assign a Port number to the input if you want to address it explicitly from a plugin or route it deliberately rather than letting FL Studio decide.

Step 2 — Link one parameter

1. Right-click the knob, slider or plugin parameter you want to control and choose Link to controller… from the menu.
2. The Remote control settings dialog opens and waits for input.
3. Move the iPhone so NueCtrl transmits. FL Studio captures the incoming controller and fills the assignment in for you — there is no need to know which CC number you are sending.
4. Before you close the dialog, set the range so the movement covers the part of the parameter you actually want, and choose the link scope: a global link belongs to FL Studio and follows you into every project, while a song link is saved inside the project file and travels with it. The dialog also exposes a mapping formula if you want the response curve to be something other than linear.
5. Close the dialog. The parameter now follows your hand.

Pick the scope deliberately. Global is right for a control you always want on the same gesture — a master filter, a send you ride on every mix. Song scope is right for assignments that only make sense inside one arrangement, and it is the safer default when you are sharing project files, because the link goes with the project instead of depending on the other machine's FL Studio configuration.

Step 3 — Link several parameters in one pass

Linking one control at a time gets tedious quickly. Arm Multilink to controllers in the toolbar, then move the phone once and click through every parameter you want in a single pass — each one picks up the same controller as you go. Right-clicking the Multilink button gives you override behaviour for parameters that already carry a generic link, which is how you replace an old assignment instead of colliding with it. Remember to switch Multilink back off when you are done, or the next control you click will quietly join the group.

To undo an assignment, right-click the parameter and choose Remove links.

Step 4 — Record the movement as automation

A linked parameter is a recordable one. FL Studio writes your movement as automation, and there are two honest ways to get it there. Arm recording with automation included in the record filter and perform the pass live against the playing arrangement — this is the take-first approach and the one that captures the feel. Or right-click the linked parameter, create an Automation Clip, and shape the curve afterwards in the playlist with full editing control. Most people end up doing both: record the gesture, then clean up the two seconds that went wrong.

Part 3 — What to map in FL Studio

NueCtrl turns iPhone motion into continuous MIDI CC, so it pays off on parameters that want to move and does nothing useful on switches. FL Studio has a handful of targets that suit a moving hand unusually well.

Patcher surface controls

This is the highest-leverage target in FL Studio and the closest thing the program has to a macro. Build your chain inside Patcher, expose a single control on the Patcher surface, and fan that one control out to several parameters across the plugins inside the patch — each with its own range. Then link NueCtrl to that one surface control. One tilt now opens a filter, pushes a delay and drives a distortion together, and you are managing exactly one link and one automation lane instead of five. If you only take one idea from this page, take this one.

Fruity Filter and Fruity Free Filter — cutoff and resonance

The classic sweep, and the reason most people want a physical controller at all. Link cutoff to your phone's tilt and the sweep inherits the acceleration and hesitation of a real hand instead of the straight lines a mouse draws. Add resonance to the same gesture through a Patcher control if you want the sweep to bite harder as it opens.

Harmor and Sytrus morph and timbre controls

FL Studio's two flagship synths are built around continuous morphing, which is exactly what a moving hand is good at and exactly what a mouse is bad at. Harmor's blend and timbre controls and Sytrus's continuous filter and operator controls all reward being performed rather than drawn. Label names differ between the two synths and have shifted across versions, so choose by function — anything that crossfades, morphs or shapes tone continuously — rather than by hunting for a specific word on the panel.

Mixer send levels and Fruity Reeverb / Fruity Delay wet

Riding a vocal into the reverb tail at the end of a line is a performance, not a drawing, and it never quite sounds right when you draw it. Link NueCtrl to a mixer send level, or to the wet control of a Fruity Reeverb or Fruity Delay on the send track, and push the vocal into the tail on the line ends before pulling it back for the next phrase.

CC1 and CC11 into sampled and orchestral instruments

Sampled and orchestral instruments respond to CC1 (modulation) and CC11 (expression) natively, which means there is no linking to do at all — send those CCs from NueCtrl into the instrument's channel and the library's own dynamics and expression layers respond directly. This is where motion control beats a mouse most obviously: a sustained string or brass line lives or dies on the shape of the CC11 curve, and a hand draws a better one than a pointer does.

Gross Beat and other continuous FX depth controls

Depth, mix and amount controls on effects are good motion targets across the board, and Gross Beat is the FL-specific case worth calling out. Stick to its smooth, continuous controls. Anything that jumps between discrete states will sound like a glitch rather than a gesture when a hand drives it, and a phone in motion never sends a clean step.

Troubleshooting

• The port is in the list but nothing responds. It is selected, not enabled. Go back to Options → MIDI Settings (F10), click the port in the Input list, then click Enable underneath. This is the single most common cause, by a wide margin.
• The port is not in the Input list at all. FL Studio enumerates MIDI devices when it launches. Finish the connection at the OS level first — pair over Bluetooth, or connect the Network / rtpMIDI session — and then restart FL Studio so the port is there to be found.
• Link to controller refuses to take. The parameter probably already carries a link from an earlier session. Right-click it, choose Remove links, then link it again.
• Random controls keep getting linked. Multilink to controllers is still armed, so every parameter you click joins the group. Switch it off in the toolbar. If it has already grabbed things you did not want, right-click each one and remove the link.
• The response is late. Check the route before you blame the buffer: Bluetooth runs around 10-15 ms, Wi-Fi around 5 ms, USB around 2 ms. If you are already on the fastest route available to you, shorten the buffer length in the Audio tab of FL Studio's settings — with an ASIO driver, that is where the rest of the round trip lives.
• There is no USB option on Windows. There is not meant to be. Getting MIDI off an iPhone over USB depends on macOS exposing the phone as a MIDI device. On a PC, install rtpMIDI and use the Wi-Fi route — it is the low-latency path on Windows.
• Wi-Fi keeps dropping. Both devices must be on the same network, and ideally the same band — a 2.4 GHz phone talking to a 5 GHz computer through a dual-band router will be flaky. Turn off Wi-Fi Assist on the iPhone so it does not silently fall back to cellular mid-take.
• The movement plays back but nothing was recorded. Automation is excluded from the recording filter. Set the filter to include automation before you record, or skip live recording entirely and create an Automation Clip from the linked parameter instead.

FAQ