The MPE spec sets per-note channels to a default bend range of plus or minus 48 semitones, while the master channel gets only two. Those two numbers cause more ruined slides than any plugin bug. When your controller and your synth disagree about them, every gesture lands at the wrong pitch.
MPE works by giving each note its own MIDI channel. That channel carries three streams of movement: pitch bend for slides, channel pressure for weight, and control change 74 for timbre. Regular MIDI sends one bend value for the whole keyboard, which is why a chord bends as a single block.
Modern synths treat those streams as ordinary modulation sources rather than a special performance mode bolted on the side. Corona 7's per-note routing into the modulation matrix is one recent example, with CC74 brightness sitting alongside the LFOs and envelopes. Getting the data that far is the part nobody documents well.
The master channel of an unused zone can be handed to the active one, which buys you up to 15 member channels. That matters if you hold dense chords with long releases, because every sounding note is occupying a channel of its own until it finishes.
A configuration message switches the zone on and carries the number of member channels you want, and a count of zero deactivates the zone completely. It also resets both bend ranges to their defaults, which is where a bend range that does not match your controller starts to hurt. Leave a LinnStrument at 24 semitones with the synth still at 48, and your slides travel half as far as your finger did.
Test it in ten seconds. Slide from one note up to a note you can name, lift your hand, then play that second note normally. Different pitches mean the per-note pitch bend ranges are out of step, not your technique.
Which means the same synth can behave differently in two formats on the same machine. Worth checking before you blame the keyboard.
Hosts add a switch of their own. Live turns MPE on per device from the Link and MIDI page of its preferences rather than per track, and in Live 12 every instrument accepts it. Arturia hides an Enable MPE button behind the settings wheel inside each instrument, and Analog Lab V does not support MPE at all as a standalone.
Live 11 supported a shorter list, covering Drift, Wavetable, Sampler, Simpler, the Arpeggiator, and the AAS instruments. Ableton also names zone configuration as a cause of silent notes, so an instrument that plays nothing at all is worth checking there before you reinstall anything.
The master channel keeps its own two-semitone range while all of this happens. A bend wheel and a per-note slide can therefore push against each other, and the pitch you hear is not the one either movement asked for on its own.
MPE also runs on synths built for MIDI mode 4. The spec permits it and then steers you away, because one monophonic channel per note caps you at 16 voices and often fewer. For sustained chords with long release times, that ceiling arrives faster than you would like.
Controller support is the last thing to check and the least forgiving of the lot. Push 1 and Push 2 send polyphonic aftertouch rather than MPE, so no amount of zone configuration will produce per-note slides from those pads, whatever the synth on the receiving end is capable of.
MPE works by giving each note its own MIDI channel. That channel carries three streams of movement: pitch bend for slides, channel pressure for weight, and control change 74 for timbre. Regular MIDI sends one bend value for the whole keyboard, which is why a chord bends as a single block.
Modern synths treat those streams as ordinary modulation sources rather than a special performance mode bolted on the side. Corona 7's per-note routing into the modulation matrix is one recent example, with CC74 brightness sitting alongside the LFOs and envelopes. Getting the data that far is the part nobody documents well.
Zones decide which channel carries which gesture
The lower zone keeps global messages on channel 1 and spreads notes across channel 2 and upward. The upper zone mirrors that from channel 16 down. Most gear implements the lower zone only, so a controller transmitting on the upper zone and a plugin listening to the lower one will trade nothing at all.The master channel of an unused zone can be handed to the active one, which buys you up to 15 member channels. That matters if you hold dense chords with long releases, because every sounding note is occupying a channel of its own until it finishes.
A configuration message switches the zone on and carries the number of member channels you want, and a count of zero deactivates the zone completely. It also resets both bend ranges to their defaults, which is where a bend range that does not match your controller starts to hurt. Leave a LinnStrument at 24 semitones with the synth still at 48, and your slides travel half as far as your finger did.
Test it in ten seconds. Slide from one note up to a note you can name, lift your hand, then play that second note normally. Different pitches mean the per-note pitch bend ranges are out of step, not your technique.
Hosts hand your plugin two different kinds of expression data
In the VST3 wrappers, MPE input processing is on by default, with the master channel at zero and member channels running from one to 14. That is 14 note channels, not the 15 the spec allows at full stretch. Steinberg maps the three MPE dimensions through the note expression interface, so a VST3 build can receive note expression events, whereas the AU build reads raw channel MIDI.Which means the same synth can behave differently in two formats on the same machine. Worth checking before you blame the keyboard.
Hosts add a switch of their own. Live turns MPE on per device from the Link and MIDI page of its preferences rather than per track, and in Live 12 every instrument accepts it. Arturia hides an Enable MPE button behind the settings wheel inside each instrument, and Analog Lab V does not support MPE at all as a standalone.
Live 11 supported a shorter list, covering Drift, Wavetable, Sampler, Simpler, the Arpeggiator, and the AAS instruments. Ableton also names zone configuration as a cause of silent notes, so an instrument that plays nothing at all is worth checking there before you reinstall anything.
Nothing breaks loudly when a plugin ignores MPE
Every MPE message is a standard MIDI message, so a synth without MPE support accepts the whole stream without a single error. It reads the most recent bend it received and applies that to every sounding note. Your expression data still fans out across all the available channels, quietly eating the channel space a multitimbral instrument was relying on.The master channel keeps its own two-semitone range while all of this happens. A bend wheel and a per-note slide can therefore push against each other, and the pitch you hear is not the one either movement asked for on its own.
MPE also runs on synths built for MIDI mode 4. The spec permits it and then steers you away, because one monophonic channel per note caps you at 16 voices and often fewer. For sustained chords with long release times, that ceiling arrives faster than you would like.
Controller support is the last thing to check and the least forgiving of the lot. Push 1 and Push 2 send polyphonic aftertouch rather than MPE, so no amount of zone configuration will produce per-note slides from those pads, whatever the synth on the receiving end is capable of.
