"Supports MPE" has become one of those DAW marketing phrases that hides more than it reveals. By 2026, MIDI Polyphonic Expression is close to table stakes — every major DAW will at minimum receive per-note pitch bend, pressure, and slide data from an MPE controller without mangling it. What separates them is what happens after that data arrives: how it's edited, visualized, and manipulated once it's sitting in a clip. That gap is where an MPE-focused composer's actual DAW choice tends to get made.
Bitwig Studio: Built Around MPE From the Start
Bitwig Studio 6, released in March, pushed this furthest of any current DAW. The update lets gain, pressure, and other per-note expressions be edited directly on notes in the timeline rather than requiring a trip into a separate editor — a change from earlier versions where only micro-pitch curves appeared directly on notes, with everything else hidden behind menu diving. The same on-clip editing now extends into the folded Drum/Hybrid editor, and the new automation gestures introduced in Studio 6 apply to expression lanes too.
This isn't a new direction for Bitwig so much as a deepening of one — the application was architected around per-note expression from early on, well before MPE controllers were mainstream, and it shows in details like how cleanly its detail editor panel handles controllers as different as a Roli Seaboard, a LinnStrument, or Expressive E's Osmose. For composers whose workflow involves drawing and redrawing expression curves after the fact — not just capturing them live — Bitwig remains the DAW most other vendors get compared against.
Logic Pro: Mature, Native, Apple-Only
Logic Pro has supported MPE natively since version 10.5, and by 10.6 it had built out a fairly complete editing environment for MPE data specifically in MIDI Mono Mode — pitch bend, pressure, and timbre each get their own editable lane, and the piano roll understands per-note channel assignment well enough that it doesn't require manual channel management the way some competitors historically have. It's a mature implementation, closer in spirit to Bitwig's than to Ableton's, with the obvious limitation that it's macOS-only and therefore off the table for anyone on Windows or Linux.
Ableton Live: Functional, With a Known Rough Edge
Ableton Live has supported MPE since Live 11, and Live 12 expanded on it further — the Live 12.2 update even shipped Expressive Chords, a free Max for Live device with 52 chord sets that respond to per-note MPE pressure, slide, and pitch bend when played through a controller like Push 3. But the DAW's longstanding rough edge is channel handling: MPE channels can get reassigned somewhat arbitrarily as notes are recorded and played back, which occasionally produces audible glitches — a held note's pitch bend jumping unexpectedly, for instance — when a channel gets reused before the previous note has fully released. Ableton has been iterating on this, and full MIDI 2.0 support (a separate but related standard) is reportedly progressing through beta testing, which should eventually give the engine cleaner high-resolution channel and controller mapping. For now, Live's MPE support is genuinely usable but benefits from a player who understands the channel-rotation quirk well enough to work around it.
Reaper: Flexible, DIY, and Occasionally More Powerful Because of It
Reaper doesn't market MPE support the way the others do, but its famously open architecture ends up being an asset here rather than a liability. Because Reaper exposes MIDI data at a lower level than most DAWs and supports JSFX scripting and community-built extensions, users have been able to build custom MPE editing and monitoring tools that in some specific cases outpace what ships natively in more "MPE-branded" competitors — at the cost of needing to assemble that toolkit yourself rather than getting it out of the box. Reaper's lightweight footprint and scriptability also make it a common choice for people building custom MPE monitoring or performance rigs rather than doing conventional studio composition, precisely because it doesn't fight you when you want to route or reinterpret expression data in a nonstandard way.
What This Means If You're Choosing
None of these four are "wrong" choices for MPE work, and the differences matter less than they might seem if your MPE use is occasional rather than central to your workflow — a synth patch that responds to slide and pressure will sound the same regardless of which of these four hosts it, as long as the controller-to-DAW handoff isn't glitching. The differences show up specifically in editing after the fact: Bitwig and Logic both let you reach in and redraw per-note curves without much friction; Ableton gets you most of the way there but with an occasional channel-handling wrinkle to manage; Reaper gets you there through configuration rather than out-of-the-box polish.
For composers whose work leans heavily on programming and refining expression after a performance — film and media composers doing detailed pass after detailed pass, for instance — that editing experience is arguably a bigger factor in DAW choice than plugin compatibility or interface at this point. MPE stopped being a differentiator between "DAWs that support it" and "DAWs that don't" a while ago. The real differentiator now is what the editor lets you do with the data once it's there.