MPE support across DAWs has improved dramatically — but setup isn't always obvious. Each DAW handles MPE routing differently, and getting it wrong means you're playing in standard MIDI mode without realising it. This guide walks through setup in the three most common DAWs for MPE work.

Before You Start

Make sure your MPE controller is recognised by your computer. Most modern MPE controllers connect via USB and are class-compliant — they'll show up automatically in your DAW's MIDI preferences without drivers. If you're using Bluetooth (Roli Seaboard RISE 2), pair the device before opening your DAW.

Ableton Live 11+

Ableton added MPE support in Live 11. Here's how to set it up:

Step 1 — Enable your controller
Go to Preferences → MIDI and make sure your MPE controller appears under MIDI input devices. Enable both Track and Remote toggles for it.

Step 2 — Load an MPE-compatible instrument
Create a new MIDI track. Load an MPE-compatible plugin (like Orchestral Xpressive). Ableton passes MPE data through to VST3 plugins automatically when the instrument supports it.

Step 3 — Arm the track and play
Click the arm button on the track (the red circle). Your MPE controller should now send per-note expression to the instrument. You'll see multiple MIDI channels lighting up in the MIDI activity indicator.

Key tip: If you're using a VST2 version of a plugin, MPE will NOT work — VST2 doesn't support MPE. Always use VST3.

Recording MPE in Ableton
Ableton records MPE as standard MIDI clips with per-note pitch bend and expression data. You can view and edit this data in the MIDI editor — each note has its own expression lane. Enable MPE view in the clip's MIDI editor to see per-note data.

Logic Pro (10.7+)

Logic added MPE support in version 10.7. It works well, but the routing is slightly different.

Step 1 — Enable your controller in Audio MIDI Setup
Open Audio MIDI Setup (found in Applications/Utilities). Your MPE controller should appear in the MIDI Studio window. Logic reads from this automatically.

Step 2 — Create a Software Instrument track
In Logic, create a new Software Instrument track. Load an AU (Audio Unit) MPE plugin. Orchestral Xpressive's AU version supports full MPE.

Step 3 — Enable MPE on the track
In the track inspector on the left, look for MIDI → MPE. Toggle it on. This tells Logic to treat incoming MIDI as MPE data rather than standard single-channel MIDI.

Step 4 — Record enable and play
Press R to record-enable the track. Play your controller. Logic will record MPE data as standard MIDI with expression attached per-note.

Key tip: Logic's piano roll has an MPE data section that displays slide, pressure, and pitch bend per note. Click the disclosure triangle at the bottom of the piano roll to reveal it.

Bitwig Studio 5+

Bitwig has the best MPE support of any major DAW — it was built with MPE in mind from early on.

Step 1 — Add your controller
Go to Settings → Controllers. Click the + button and add your MPE controller. Bitwig has presets for most MPE controllers (Roli, LinnStrument, Osmose, etc.) — select yours for optimised behaviour.

Step 2 — Load an instrument
Create a new Instrument track. Load any MPE-compatible VST3 or Bitwig's own instruments (The Grid, Polymer, etc. all support MPE natively).

Step 3 — That's it.
Bitwig routes MPE automatically. There's no extra toggle. Per-note expression works out of the box.

Bitwig's MPE editor
Bitwig's note editor is the most powerful MPE editor available in any DAW. Each note displays its slide, pressure, and pitch bend data as coloured curves inline within the note. You can draw, edit, and sculpt expression data with precision.

Common Problems and Fixes

No per-note expression despite MPE being enabled
→ Check you're using VST3 (not VST2) or AU. VST2 does not support MPE.

All notes pitch-bend together
→ Your plugin may not have MPE enabled internally. Check the plugin settings — some plugins have an MPE toggle inside the interface.

Notes are stuck or doubling
→ MIDI feedback loop. In your DAW MIDI preferences, make sure the MPE controller's output is NOT being fed back into your track as input.

Latency on expression data
→ Reduce your audio buffer size. Expression data is MIDI, so audio latency doesn't directly affect it — but a larger buffer can make the response feel sluggish. Aim for 128 samples or lower when playing live.

Getting the Most from MPE with Orchestral Xpressive

Orchestral Xpressive's default patch mapping is designed to feel natural across all three DAWs. CC74 (Slide) controls timbre per note, pressure adds dynamics, and pitch bend is set to ±48 semitones for maximum expressive range.

Start with the Cinematic Orchestra — Brass Ensemble patch and experiment with pressure on sustained notes. The swell response is calibrated for live performance, not just studio work.