If you produce in FL Studio and have been waiting for native MPE support, the wait isn't over — and according to Image-Line, it isn't coming at all in its current form. The company has confirmed that MPE will not be added to FL Studio, with development instead aimed directly at full MIDI 2.0 implementation. It's a notably different strategy from most of the rest of the DAW field, and worth unpacking for anyone choosing a MIDI Polyphonic Expression controller as a primary instrument.

Where the other major DAWs stand

Over the past several years, MPE support has gone from a niche feature to close to table stakes among the DAWs most associated with sound design and expressive performance. Ableton Live added MPE with Live 11 and has expanded it in Live 12, with native support in stock instruments like Wavetable, Drift, and Sampler. Bitwig Studio built per-note MPE handling in early and has continued adding dedicated expression-editing tools release over release. Logic Pro supports MPE through its MIDI Mono Mode implementation and works with controllers from ROLI and others out of the box. Reaper, Cubase, and Studio One have all added MPE-aware editing to varying degrees as well.

FL Studio is a conspicuous exception. Despite years of user requests on the Image-Line forums — many specifically citing controllers like ROLI Seaboard, LinnStrument, and Ableton Push — the feature has never landed, and the company has now been explicit that it's not on the roadmap in its current MPE-1.0 form.

The stated reasoning: skip ahead to MIDI 2.0

Image-Line's position is that building a full MPE implementation now would mean investing engineering time in a specification that MIDI 2.0 effectively supersedes. MIDI 2.0 natively supports per-note pitch bend, per-note aftertouch, and per-note slide/CC data as part of the protocol itself, rather than as a channel-per-note workaround layered on top of MIDI 1.0 — which is fundamentally how MPE works. From a pure engineering standpoint, building MIDI 2.0 support once could deliver equivalent (and in some respects richer) expressive capability without maintaining a separate MPE compatibility layer.

The tradeoff is timing. MIDI 2.0 adoption across hardware controllers, operating systems, and other DAWs is still uneven — plenty of MPE controllers on the market today were designed and firmware-updated with MPE-over-MIDI-1.0 in mind, not native MIDI 2.0. Producers who bought into an MPE controller expecting broad DAW support now have one major platform betting on a future spec instead of the one that's actually running on most rigs in use today.

Workarounds exist, but they're workarounds

FL Studio users haven't been left with nothing. Community-built solutions — most notably routing controller output through the free, open-source MPE Emulator plugin or similar MIDI shape-shifting tools — let users approximate MPE-style per-note expression inside FL Studio's existing MIDI handling, translating incoming pitch bend, pressure, and CC74 data into something the DAW can use. It works, but it's a layer most users of Ableton, Bitwig, or Logic simply don't need to think about.

What this means for producers choosing a DAW

For musicians whose workflow depends on an MPE controller, this is a genuinely practical consideration when picking a primary DAW — not just a spec-sheet curiosity. If FL Studio is your home base and you're evaluating a Seaboard, Osmose, or LinnStrument, budget time for a workaround rather than assuming plug-and-play support. If you're MPE-first and DAW-agnostic, the current landscape still points toward Bitwig, Ableton, or Logic as the smoother path.

Whether Image-Line's bet on MIDI 2.0 pays off depends largely on how quickly the rest of the industry — controller manufacturers, plugin developers, and operating systems — finishes the transition it's betting on.