FL Studio users have been asking for MPE support for years. In 2026 Image-Line's answer became clear, and it was not the one most people expected: rather than implementing MPE, the company is targeting MIDI 2.0 per-note controllers directly.

That decision has generated a fair amount of confusion, some of it justified. It is worth separating what the two specifications actually do from what the arguments about them tend to assume.

The Two Approaches, Briefly

MPE is a convention built on top of MIDI 1.0. It takes the existing protocol and agrees on a way to use it: one note per channel, so that each note gets its own pitch bend, channel pressure and CC74. Nothing in MPE requires new hardware, new cables or new drivers. It works because everyone agreed to read the same old messages in the same new way.

That elegance is also its ceiling. MIDI 1.0 gives you 7-bit resolution for most controllers and 14-bit for pitch bend, and MPE inherits both. It gives you a maximum of 15 member channels, which caps polyphony at 15 simultaneously expressive notes. And every note consumes a channel, so channel management becomes something instruments have to actively negotiate.

MIDI 2.0 solves those constraints at the protocol level. Per-note controllers are a native message type — no channel juggling required, because the note itself carries an identifier. Resolution jumps to 32 bits. Polyphony is not limited by channel count. Devices negotiate capabilities with each other through Property Exchange rather than relying on the user to configure matching bend ranges on both ends.

On paper, MIDI 2.0 is straightforwardly better. Image-Line's position is essentially that building MPE support in 2026 means investing in a workaround for limitations that the newer protocol removes outright.

Why That Argument Is Not the Whole Story

The counterargument is short: the controllers people own today speak MPE.

The Osmose, the LinnStrument, the Seaboard line from ROLI, the Haken Continuum, the Striso board — these are MPE instruments. Some can emit MIDI 2.0, most cannot, and firmware alone does not always close the gap. A DAW that supports MIDI 2.0 per-note controllers but not MPE will, in practice, do nothing useful with the majority of expressive hardware currently on desks.

There is a technical bridge: MIDI 2.0 also supports polyphonic pitch bend, slide and aftertouch, so an MPE controller's output could be translated into MIDI 2.0 per-note messages at the input stage. Whether a given host does that translation cleanly — and whether it survives round-tripping through recording, editing and playback — remains to be seen. "Should work in theory" and "works with your Seaboard on Tuesday" are different claims.

What This Means Practically

For anyone choosing a DAW around expressive playing right now, the position is unchanged. Bitwig Studio remains the most complete MPE environment, with per-note expression editable directly on notes in the timeline — Bitwig 6, released in March 2026, extended this with on-clip expression editors for gain, pressure and the rest, removing a layer of menu diving. Ableton Live and Logic Pro both handle MPE competently. Reaper handles it with configuration. FL Studio, for now, does not handle it at all.

For the longer term, the honest answer is that MIDI 2.0 adoption is slower than its advocates hoped and faster than its sceptics claim. The protocol has been ratified for years; broad hardware support is still arriving. Image-Line may well be right that MPE is a transitional standard. It may also be that the transition takes long enough that skipping it costs the company a segment of users who simply buy a different DAW.

The Non-Answer That Is Actually the Answer

You do not have to pick a side. MPE is not going to stop working — it is a usage convention over MIDI 1.0, and MIDI 1.0 is not going anywhere. Instruments and hosts will support both for a long time, in the same way that USB devices still ship with fallbacks.

Buy the controller you want to play, and choose the DAW that works with it today. If a manufacturer tells you MIDI 2.0 makes your MPE gear obsolete, they are selling something. If someone tells you MIDI 2.0 is vapourware, they are not watching the spec closely enough.

For a deeper look at how individual hosts differ in their MPE handling, the MIDI Association's MPE documentation is the primary source worth reading.

Sources: MIDI.org · Image-Line forum · Synth Anatomy