Learn — By WATMM Desk —

MPE explained: MIDI Polyphonic Expression, channel per note, and when it matters

MPE gives every sounding note its own MIDI channel so pitch bend and other expression can move one note at a time inside ordinary MIDI 1.0. Here is how it works, the zone and master-channel idea from the MIDI Association spec, which instruments use it, how to switch it on in a DAW, and when it is worth the trouble. Sources checked on 30 Oct 2026.

Key facts

  • MPE (MIDI Polyphonic Expression) was ratified by the MIDI Manufacturers Association on 28 Jan 2018; the current MIDI Association document is M1-100-UM v1.1, which replaces RP-053 v1.0.
  • MPE uses MIDI 1.0 messages: each sounding note gets its own channel from Note On to Note Off, so channel-wide messages such as Pitch Bend and Control Change reach one note.
  • Channels are grouped into Zones, and each Zone has a Master Channel that carries Program Change, pedal data and overall Pitch Bend for the whole Zone.
  • If more notes sound than there are channels, notes share channels and lose individual control but keep sounding.
  • In Ableton Live you enable MPE Mode per controller in the Link, Tempo & MIDI settings, and can edit per-note pitch, slide and pressure.

MPE, short for MIDI Polyphonic Expression, is a way of using ordinary MIDI so that every note in a chord can be bent, pressed and shaped on its own. The MIDI Association describes it as "a method of using MIDI which enables multidimensional controllers to control multiple parameters of every note within MPE-compatible software" (MIDI Association). The MIDI Manufacturers Association ratified it on 28 Jan 2018 (MIDI Association), after Japan's AMEI released it in November 2017 (Wikipedia).

The current document is M1-100-UM MIDI Polyphonic Expression v1.1, which replaces the earlier RP-053 version 1.0, and the MIDI Association files it under MIDI 1.0 because it is built from "MIDI 1.0 messages" (MIDI Association). No new cable, driver or protocol is needed.

If you want the wider controller picture first, start with our MIDI controller basics guide; this page goes deeper on MPE alone.

The problem: MIDI 1.0 expression is per channel

In classic MIDI 1.0, a keyboard sends every note on one channel. Messages like Pitch Bend and most Control Changes apply to the whole channel, so bend the wheel while holding a chord and every note bends together. That is fine for a lead line and useless if you want one finger of a chord to slide up while the others hold.

How MPE fixes it: one channel per note

MPE's trick is simple. Each sounding note is given its own MIDI channel for its life, from Note On to Note Off, so messages that normally affect a whole channel now affect just that note. The MIDI Association names Pitch Bend and Control Change as messages that can be addressed to individual notes this way (MIDI Association). Wikipedia puts it the same way: MPE "works by assigning each note to its own MIDI channel" so controller messages apply note by note (Wikipedia).

Three ideas from the spec are worth knowing (MIDI Association):

  • Zones. A Registered Parameter Number message sets how many channels are used, and channels are split into Zones.
  • The Master Channel. Each Zone has one Master Channel for messages that should affect everything: Program Change, pedal data and an overall Pitch Bend for the whole Zone. The remaining channels carry the individual notes.
  • Running out of channels. MIDI has 16 channels per port. If more notes sound than there are channels in the Zone, notes share channels and lose individual control, but they keep sounding.
MIDI 1.0 as usually playedMPE
Channels used by one instrumentOneOne per sounding note, plus a Master Channel
Pitch Bend on a chordMoves every noteMoves only the note you touch
Global messages (program, sustain)Same channel as the notesMaster Channel of the Zone
New hardware protocol neededn/aNo, it is MIDI 1.0 messages

The press release also says the spec defines how Aftertouch is handled; on MPE controllers this usually shows up as per-note pressure, which Ableton labels "Poly Aftertouch/MPE Pressure" (Ableton). The exact controller numbers and default bend ranges are set in the spec document itself; read it rather than forum lore if you are configuring hardware by hand.

Controllers and synths that use it

MPE controllers are surfaces that sense more than "which key, how hard". Wikipedia lists the Continuum Fingerboard, LinnStrument, ROLI Seaboard, Sensel Morph and Eigenharp as instruments that let you control pitch, timbre and other nuances of individual notes within a chord (Wikipedia). The MIDI Association's adoption release names ROLI's Seaboard GRAND, Seaboard RISE and BLOCKS hardware, and says Roger Linn demonstrated the LinnStrument in its 2018 MPE live chat (MIDI Association).

On the sound side, the same release names Moog's Animoog and Apple's Logic as products that take advantage of MPE (MIDI Association). In Ableton Live, "many Live devices support MPE and include MPE presets" (Ableton).

The catch is that both ends must speak MPE. An MPE controller playing a non-MPE synth will either bend everything together or play each note on a different channel the synth may not be listening to.

DAW setup: the Ableton Live example

Every DAW names things differently, but the steps are the same shape. In Live 12 (Ableton):

  1. Enable MPE for the controller. Turn on MPE Mode for that controller in the Link, Tempo & MIDI settings.
  2. Arm a track with an MPE-capable instrument. When an MPE-enabled controller is the track input, Live locks input routing to all channels, because the notes arrive spread across them.
  3. For third-party plug-ins, MPE settings live in the context menu of the plug-in's title bar, and the on/off state is saved with that device's default configuration.
  4. Edit what you recorded. Live shows per-note Pitch (per-note pitch bend), Slide (per-note Y-axis) and Pressure (Poly Aftertouch/MPE Pressure), alongside velocity and release velocity.

If a note bends the wrong amount, the usual cause is a mismatch between the bend range the controller assumes and the one the synth uses. Set both sides to the same value.

When it matters, and when it doesn't

It matters if you play sounds that are meant to move: strings, brass, voice-like leads, slides between notes, or chords where one voice swells while the rest stay put. It also matters if you are recording expressive takes you want to edit later, note by note.

It doesn't matter much if you mostly program drums, trigger loops, step-sequence basslines or draw notes with a mouse. Without a controller that senses per-note movement, MPE has nothing to carry.

What we think

MPE is one of the smartest moves MIDI has made: rather than wait for a new protocol, it bent an old rule (one instrument, one channel) and got per-note expression working on gear people already owned. That is also its weakness. It spends up to 15 of your 16 channels on a single instrument, and it only works when controller, DAW and synth all agree on the zone and the bend range, which is where most "MPE doesn't work" threads end up.

Our advice: don't buy an MPE controller to fix your music; buy one if you already hear the slides and swells in your head and a keyboard keeps getting in the way. Before buying, check that the two or three synths you actually use list MPE support, and treat the spec as your reference for setup, not a forum post. The spec is a free read on the MIDI Association site, and v1.1 is the version to check against (MIDI Association).

FAQ

Is MPE part of MIDI 2.0? No. The MIDI Association lists MPE as a MIDI 1.0 specification built from MIDI 1.0 messages (MIDI Association).

Do I need special cables? No. It is ordinary MIDI messages, so any MIDI connection that carries all 16 channels works.

What happens if I play more notes than there are channels? Notes start sharing channels and lose their individual expression, but they keep sounding (MIDI Association).

Can I use an MPE controller with a non-MPE synth? You can play notes, but per-note bends and pressure won't behave as intended. Turn MPE off on the controller for that synth.

Sources

  1. MPE (MIDI Polyphonic Expression) specification, The MIDI Association (primary source). Accessed 30 Oct 2026.
  2. MIDI Polyphonic Expression (MPE) Specification Adopted!, The MIDI Association (primary source). Accessed 30 Oct 2026.
  3. MIDI, Wikipedia. Accessed 30 Oct 2026.
  4. Editing MPE, Ableton Reference Manual Version 12, Ableton (primary source). Accessed 30 Oct 2026.

Researched with AI assistance, written and checked by WATMM Desk.

Subscribe to We are the music makers

One email a week: the music-tech and AI-in-music news that mattered, and what we think about it.

Sign-ups open soon.