You plug in an MPE controller, load an MPE-capable plugin, slide your finger sideways one semitone — and the note leaps two octaves. Or the opposite: you throw your whole hand across the surface and the pitch barely wobbles.
Neither is a bug. In almost every case it is a pitch bend range mismatch, and it is the single most common reason people conclude that a plugin's MPE implementation is broken when it is working exactly as designed.
What Pitch Bend Range Actually Means
MIDI pitch bend is not sent in semitones. It is sent as a 14-bit number from 0 to 16383, with 8192 as centre. That number means nothing on its own — it is a percentage of a range, and the range is defined separately.
If the range is ±2 semitones, a value of 16383 means "bend up 2 semitones." If the range is ±48 semitones, the exact same value means "bend up four octaves." The number is identical. Only the agreed range differs.
In conventional MIDI this rarely bites you, because ±2 is a near-universal default and everything quietly agrees. MPE breaks that assumption, because MPE uses pitch bend for something entirely different.
Why MPE Uses Huge Bend Ranges
On an MPE controller, sideways finger movement is not a pitch bend wheel. It is your note position on a continuous surface. Sliding from C to the G above it is a seven-semitone slide, and the controller expresses that as pitch bend on that note's channel.
For that to work, the bend range has to be wide enough to cover any slide a player might make. Hence the MPE convention: ±48 semitones (four octaves) per member channel. That is the default on the LinnStrument, the Expressive E Osmose, most ROLI surfaces, and the Haken Continuum family.
The master channel is a separate matter and usually stays at ±2, because that channel still carries a conventional pitch bend wheel for the whole zone. The MPE specification describes both, and it is the per-note member channel range that causes the trouble.
The Arithmetic of Being Wrong
Once you see it as a ratio, the symptoms become diagnostic:
- Controller at ±48, plugin at ±2 → everything is 24× too big. A one-semitone slide jumps two octaves. Light vibrato sounds like a siren.
- Controller at ±12, plugin at ±48 → everything is 4× too small. Big gestures produce timid movement. Slides feel rubbery and never arrive.
- Controller at ±2, plugin at ±48 → per-note bend is effectively dead. Notes snap between pitches instead of gliding.
If your symptom is "24× too much," you have the classic ±48-vs-±2 mismatch and you can stop reading diagnostics here.
Fixing It: Controller Side
Every MPE controller exposes this somewhere.
LinnStrument — Global Settings, under Bend Range, with a 48 option; Roger Linn's MPE explainer covers the reasoning. Osmose — in MIDI settings alongside the MPE zone configuration; check the current Expressive E documentation for your firmware, since the menu has moved between 2.x releases. ROLI Seaboard — in ROLI Dashboard / Connect. Continuum / EaganMatrix — in the instrument's own editor, with different conventions depending on whether you run MPE mode or the native Continuum protocol.
A general rule: do not change the controller unless you have a reason to. ±48 is the convention, and moving away from it means every plugin you own is now the odd one out instead of just this one.
Fixing It: Plugin Side
This is usually the side that is actually wrong.
Well-behaved MPE plugins respond to the MPE Configuration Message (MCM) that the controller sends when it connects, and to the RPN 0 pitch bend sensitivity message that follows. If your plugin honours those, the range negotiates itself and you never think about it.
Many plugins do not. Common patterns to look for:
- A "Bend Range" or "MPE Bend" field in the plugin's MIDI or settings panel — set it to match your controller, usually 48.
- A global MPE on/off toggle that must be enabled before the bend-range field does anything at all. Plenty of plugins ship with MPE off by default even when they advertise support.
- Separate glide and bend controls, where glide is legato portamento and has nothing to do with MPE. Changing the wrong one is a classic time sink.
- Plugins that hard-code ±48 and ignore whatever you set. These are fine with a standard controller and unfixable with a non-standard one — another argument for leaving the controller at 48.
Fixing It: The DAW in the Middle
Your DAW is a third party to this negotiation, and it can quietly break an otherwise-correct chain.
In Ableton Live, MPE has to be enabled per-track, and the MPE settings panel in the MIDI clip editor carries its own pitch range value that affects how recorded bend data is displayed and played back.
In Bitwig Studio, per-note expression is native and generally passes through cleanly, but note-expression data drawn by hand in the editor is written in semitones and can exceed what the destination plugin will honour.
In Logic Pro, MPE is enabled per-track and the project's MPE settings affect recorded data on capture — meaning a wrong setting is baked into the take, not just the monitoring.
That last point is the one worth internalising: check the range before you record, not after. A take captured against the wrong range is not always cleanly rescalable, because pitch data may have clipped at the ceiling on the way in. Clipped bend data is gone.
A Thirty-Second Test
Before a session, play a single note and slide up exactly one octave on the surface. If the pitch arrives at the octave, the chain is correct end to end. If it overshoots wildly, your plugin is set too high relative to the controller. If it barely moves, too low.
Do this once per new plugin and you will never debug it mid-take. It is the MPE equivalent of checking your tuning — mildly tedious, and much cheaper than discovering the problem after the good take.
Sources: MIDI.org MPE specification, Roger Linn Design: What is MPE?, Sound On Sound: The ABC of MPE