New synth plugins launch every week, and many are excellent but have no MPE support. A recent example is Audio Damage's Sandbender, a four-operator FM synth that emphasises playability on desktop and iOS. Coverage highlights its playing focus, not an MPE feature, so check the manual before assuming otherwise. If you own an MPE controller, you can still use plugins like this. You just need to know what you will and will not get.
Why non-MPE plugins behave strangely
An MPE controller sends each note on its own MIDI channel, with per-note pitch bend, pressure and slide (CC74). A plugin without MPE support typically listens on a single channel or treats all channels as one. The results vary:
- It may ignore the extra channels entirely, so only one note sounds.
- It may merge channels, so pitch bend from one finger bends every note.
- It may work for single-note lines but fall apart on chords.
None of this means the plugin is broken. It was simply designed for conventional MIDI.
Step 1: Check what the plugin supports
Look in the plugin's manual or settings for "MPE", "multi-channel" or "per-note expression". Some plugins do not use the MPE label but still respond to polyphonic aftertouch. In that case, a controller or DAW setting that converts pressure to polyphonic aftertouch may work better than full MPE. Check your controller's documentation for such an output mode.
Step 2: Switch the controller to a single-channel mode
Most MPE controllers offer a mode that sends everything on one channel. Switch to it for non-MPE plugins. You lose per-note bend, but you keep the keyboard and often channel pressure. Pitch bend now affects every held note, which is how a conventional keyboard behaves.
Step 3: Reduce the bend range
If your controller was set to a wide MPE bend range, such as 48 semitones, pitch bend will sound wildly exaggerated on a plugin expecting 2. Set the controller to match the plugin, and check whether the plugin lets you change its bend range.
Step 4: Map the expression you can keep
Even without MPE, the plugin probably has useful targets. Many allow you to map channel pressure or CC74 to filter cutoff or another parameter through a modulation matrix or MIDI learn. You get shared, not per-note, expression, but it can still make a pad or lead more alive. In your DAW, a MIDI effect or a channel filter can also route a single stream of CC data to the plugin.
Step 5: Use workarounds for polyphony
If you want per-note behaviour from a plugin without MPE, one workaround is to load several instances, each on its own MIDI channel, and split your controller's output across them. This is resource-heavy and fiddly, and it only suits small numbers of voices. For most people, it is simpler to reserve non-MPE plugins for parts where shared expression is enough, and use MPE-capable instruments for the lead parts that benefit from per-note control.
Know the limits
Expect compromises. Chords will not bend independently, and per-note vibrato or slide will not be available unless the plugin supports it. That is a reason to treat MPE support as a feature worth checking before you buy, not a deal-breaker for every plugin. Trial versions are the safest way to test a particular combination of controller, DAW and instrument.
A quick test routine
Play a single held note, then add a second finger and slide only one note. If both notes bend, the plugin is merging channels. Next, press harder on one note and listen for changes on the others. This two-minute test tells you exactly what the plugin does with your controller, so you can choose the right mode and mappings before you start a project.