If you have ever plugged a sustain pedal into an MPE setup and watched notes hang forever, cut off early, or ignore the pedal completely, you have met one of MPE's quieter complications. The cause is architectural: MPE spreads each note across its own MIDI channel, while a sustain pedal is meant to affect everything at once.
How MPE splits up a performance
The MPE specification, maintained by the MIDI Association, assigns each sounding note its own member channel. That is what lets one finger bend pitch while another stays steady, because pitch bend is a channel-wide message. Pressure and slide (usually CC74) work the same way.
The spec also defines a master channel for each zone, typically channel 1 for the lower zone. Messages that should apply to the whole zone, rather than to a single note, are sent there. Sustain (CC64) is a classic example: it is a global gesture, so a compliant controller or pedal sends it on the master channel.
Where things go wrong
A synth that follows the spec receives CC64 on the master channel and applies it to every member channel in that zone. Problems appear when something in the chain does not:
- A pedal sends CC64 on the wrong channel. A generic controller may send it on channel 1 while your MPE zone uses a different layout, or on a single member channel, so only one note sustains.
- A plugin ignores master-channel messages. Some instruments process only member channels, leaving the pedal inert.
- A DAW filters or remaps channels. Hosts differ in how they record and play back MPE, so global messages can be dropped or merged during recording.
The symptoms look different but the cause is the same: the pedal message is not reaching the channels that hold your notes.
Practical fixes
Start by confirming what your instrument is actually sending. A free MIDI monitor will show the channel number attached to each CC64 event. If the pedal arrives on channel 1 and your plugin ignores it, check the plugin's MPE settings, since some offer an option for how global controllers are handled.
If the pedal plugs directly into the controller, look at the controller's documentation, as hardware such as Expressive E's Osmose and LinnStrument handle pedal inputs in their own ways and often let you choose the behavior. If the pedal goes into a separate MIDI interface, you may need a channel-remapping tool to move CC64 onto your zone's master channel.
Inside the DAW, check how your host records MPE. Bitwig Studio and Ableton Live both capture MPE per note, but it is worth recording a short test with the pedal pressed and listening back before an important session. A quick test pass takes a minute and can save a ruined take.
Pedal behavior is also a design choice
Not every player wants a traditional piano-style sustain. Because MPE notes are independent, some instruments offer sustain that only holds notes already played, and others let a footswitch trigger a different function altogether. When shopping for a synth, it is useful to ask whether the pedal acts per zone, whether it affects the release stage only, and how it interacts with note-off events.
A simple checklist
Before you perform or record, run through these steps: play a chord, press the pedal, release your fingers, and confirm that all notes hold. Then release the pedal and make sure all notes end together. Repeat after bending a note, since pitch-bend resets can also reveal hanging-note problems.
Global messages are one of the few places where MPE asks you to think about the whole instrument rather than individual fingers. Once you know that sustain lives on the master channel, most pedal mysteries turn into straightforward routing questions. For more on how channels and zones fit together, see the MIDI Association's specification and your controller's manual.