How to Use Your iPhone as a MIDI Controller in Bitwig 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 computer running Bitwig Studio — macOS, Windows or Linux. Bitwig is one of the few DAWs in this series with a native Linux build, and the controller and modulator workflow below is identical on all three platforms.
• One connection route — Bluetooth, the same Wi-Fi network as your computer, or a Lightning / USB-C cable. Note that the USB route depends on macOS; see the caveat in Part 1.

Part 1 — Connect your iPhone

This part is the same for every DAW, because it happens at the operating-system level before Bitwig 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 Bitwig 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.

Part 2 — Bitwig Studio setup

Bitwig keeps an explicit list of the controllers it is willing to talk to, and that list is the gate for everything else on this page. A MIDI port your operating system can see is not automatically a port Bitwig will accept a mapping from. Get the list right first and the rest of the setup takes about two minutes.

Step 1 — Add NueCtrl under Settings → Controllers

1. Open the Dashboard — the full-window panel you reach from the Bitwig logo in the top-left corner of the window.
2. Go to Settings, then Controllers.
3. Bitwig auto-detects a great many devices, so NueCtrl may already be sitting in the list. If it is, confirm that the MIDI input it is pointed at is the right one and move on.
4. If Bitwig has not recognised it, click Add Controller and pick one of the Generic entries — a generic MIDI keyboard or generic MIDI controller, depending on your version. NueCtrl sends ordinary continuous controller messages, so a generic entry is all it needs; there is no NueCtrl controller script to install.
5. Select the MIDI input port carrying NueCtrl: NueCtrl BLE for Bluetooth, the session name for Wi-Fi, or NueCtrl for USB.

Step 2 — Bind a parameter from the mapping panel

1. Open the mapping panel using the panel controls at the top right of the Bitwig window.
2. With the panel open, tilt the iPhone so the incoming CC registers — the panel shows the controller Bitwig just heard.
3. Click the parameter you want to bind. The assignment is made immediately and appears in the panel's list, where you can remove it or adjust its range later.
4. Close the panel when you are done. Mappings are stored with the project, so a template project with your NueCtrl assignments already in place is worth building once.

Step 3 — The MIDI modulator, which is where Bitwig pulls ahead

Every Bitwig device carries modulator slots, and this is the feature that makes Bitwig genuinely different from the other DAWs in this series. Add a MIDI modulator to a device, set it to the CC number NueCtrl transmits, and you now have a live modulation source sitting inside the device itself rather than a single point-to-point assignment.

Drag that modulator's amount onto a parameter and you set a depth for that one destination. Drag it onto a second parameter and you set an independent depth there — and the depth can be negative. Concretely: one tilt of the phone can open a filter cutoff and simultaneously pull a reverb send down, each by an amount you choose, without a single automation lane and without duplicating the mapping. Add a third and fourth destination and the gesture keeps its shape across all of them. Nothing else covered in this guide series does that as cleanly, and it is the reason a motion controller and Bitwig fit together unusually well.

Step 4 — Record the pass

Set the automation write mode in the transport and record while you play the part. On a direct mapping, Bitwig writes automation onto the target parameter exactly as if you had dragged it with the mouse. Where you are using a modulator, you have a second and often better option: leave the modulation routing alone and automate the modulator's amount instead. That way the recorded lane describes how much influence the gesture has over time, while the gesture itself stays live and responsive.

Part 3 — What to map in Bitwig Studio

NueCtrl turns iPhone motion into continuous MIDI CC, so it belongs on parameters that want to move, not on switches. Bitwig's modulation system means the interesting targets are not always the obvious ones.

One MIDI modulator into several destinations

The headline technique, as a recipe: put the devices you want to move together into a single device chain, add a MIDI modulator to the first device, point it at the CC NueCtrl is sending, then drag its amount onto every parameter that should respond. Give the ones that should open a positive depth and the ones that should close a negative one. You have now built a Macro-style gesture with per-destination curves and no automation to manage.

The Grid — Poly Grid and FX Grid

The most open-ended target in any DAW covered by this series. Route the CC into a Grid patch through a modulator and it can drive anything you have built inside: an oscillator's pitch, a filter's cutoff, a delay time, the mix of two signal paths, the rate of something you patched yourself. Because a Grid patch is yours, the gesture is not limited to what a plug-in developer chose to expose.

Polymer and Phase-4 continuous parameters

Bitwig's own synths are full of parameters worth performing rather than programming. Polymer's filter cutoff is the obvious first target and rewards a hand movement immediately. Phase-4 is the more interesting one: its phase-modulation and oscillator morph controls change timbre in ways that sound composed when a hand shapes them and mechanical when an LFO does.

Nested chains and layer crossfades

Bitwig lets you nest device chains inside layer and selector devices, and the control that moves between those layers is continuous. Map it and you can cross from one layer to another by hand — a soft sound into a hard one over four bars, at the pace the music actually wants rather than the pace a drawn ramp gives you.

Send levels and FX device wet controls

Riding a send to a reverb or delay is a mix move that rarely sounds right when drawn with a mouse, because it is fundamentally a performance. The same applies to the wet or mix control on an FX device. Both are natural single-destination mappings, and both are good places to start before you build anything more elaborate with modulators.

CC1 and CC11 into sampled and orchestral instruments

If you run orchestral or sampled libraries in Bitwig, send NueCtrl's output on CC1 (modulation) and CC11 (expression) and the library's own dynamics and expression layers respond directly. No mapping and no modulator are involved — the instrument already listens to those controllers. Sustained string and brass lines live or die on the shape of the CC11 curve, and that shape is exactly what a moving hand is good at.

Troubleshooting

• Nothing maps, and nothing reacts at all. The port was never added under Settings → Controllers. Bitwig ignores MIDI inputs that are not on its controller list, so mapping is impossible until you add one. Check this first, every time.
• The controller entry exists but still nothing happens. The entry is pointed at the wrong MIDI input. Open its settings and confirm the input is NueCtrl BLE, the Wi-Fi session name, or NueCtrl — whichever route you actually connected.
• Clicking a parameter does not bind it. The mapping panel is closed. Bitwig only captures an assignment while that panel is open; with it closed, a click just moves the parameter.
• The mapping looks correct but you hear nothing. A distinctly Bitwig failure mode: the modulator's amount for that destination is still at zero. The routing exists, the CC is arriving, and the depth is nil. Drag the amount up on the destination and it comes alive.
• The port is missing from the list entirely. Bitwig enumerates MIDI at launch. Finish the connection at the OS level first — pair over Bluetooth, or connect the network session — then restart Bitwig so the port is available to add.
• Movement is audible but late. Bluetooth runs around 10-15 ms, Wi-Fi around 5 ms, USB around 2 ms. Change route before you blame the DAW. If you are already on USB, reduce the audio block size in Bitwig's audio settings — a large block adds latency on top of whatever the MIDI route costs.
• You are on Windows or Linux and there is no USB option. There is not one: the USB path depends on macOS exposing the iPhone as a MIDI device. Use Wi-Fi with rtpMIDI on Windows, or an RTP-MIDI service on Linux, and expect roughly 5 ms.

FAQ