MPE was built to solve a specific problem within the constraints of classic MIDI 1.0: give each note its own pitch bend, pressure, and timbre control by spreading notes across multiple channels. It was a clever workaround, and it's why MPE controllers from Roli, Expressive E, and Haken Audio all speak the same underlying language today. MIDI 2.0 was designed, in part, to make that workaround unnecessary — giving every note native per-note control without channel-splitting tricks. Nearly six years after the spec was ratified, 2026 has been the year that infrastructure genuinely started catching up.
Profiles: MIDI 2.0's Answer to Compatibility Chaos
One of the least glamorous but most consequential pieces of MIDI 2.0 is the Profile system, and it saw real movement at NAMM 2026. A profile is a standardized behavioral contract that a controller and a sound engine can negotiate automatically over MIDI-CI (MIDI Capability Inquiry) — essentially, a way for two devices to agree in advance on what a given controller message should mean, rather than leaving it to guesswork or manufacturer-specific documentation.
The Piano Profile, a focus of MIDI Association discussion this year, standardizes how devices interpret velocity curves, pedal behaviors (sustain, soft, and sostenuto), and other registered controllers specific to piano-style playing. In practice, that means a piano-focused controller and a virtual instrument from two different manufacturers can negotiate a shared understanding of what a half-pedal position or a specific velocity curve should produce, without a user manually mapping CCs or hunting through a manual. For MPE users, the same underlying negotiation mechanism — MIDI-CI — is what eventually enables per-note expression to be recognized and configured automatically rather than requiring a controller-specific MPE zone setup in every new plugin.
Transport Layer Progress: USB, Network, and BLE
Alongside profiles, transport adoption has kept moving through 2026. The MIDI Association and Japan's AMEI have already finalized the USB MIDI 2.0 and UDP-based Network MIDI 2.0 transports, meaning MIDI 2.0 data can now travel over a standard USB connection or a local network without falling back to MIDI 1.0 compatibility mode. Work is now underway on a Bluetooth Low Energy MIDI 2.0 transport, which would bring the same per-note resolution and profile negotiation to wireless controllers — relevant for the growing number of MPE-style instruments, like Roli's Airwave, that ship with wireless connectivity as a core feature rather than an afterthought. The MIDI Association has also indicated it wants to push the W3C toward a Web MIDI 2.0 specification, which would extend these capabilities into browser-based tools and web-hosted DAWs.
Windows Joins macOS on Native MIDI 2.0
The platform side of this story reached a milestone in February 2026, when Microsoft announced general availability of Windows MIDI Services in Windows 11 — a fully rewritten MIDI stack with native support for both MIDI 1.0 and MIDI 2.0, rolling out to in-support Windows 11 releases. That puts Windows on more equal footing with macOS's existing native MIDI 2.0 support, closing a gap that had previously made cross-platform MIDI 2.0 development more fragmented than it needed to be for hardware manufacturers and plugin developers alike.
Why MPE Players Should Care
MIDI 2.0 doesn't obsolete MPE — most current MPE controllers and instruments still communicate over MIDI 1.0 with MPE's channel-per-note convention, and that isn't changing overnight. But the profile and transport work happening in 2026 is laying the groundwork for a future where per-note expression is a native, auto-negotiated feature of the protocol itself rather than a specification bolted onto MIDI 1.0's limitations. As more DAWs, plugins, and controllers add MIDI 2.0 support alongside their existing MPE implementations, the practical experience for musicians — less manual channel configuration, more automatic recognition of what a controller can do — should start to improve even for instruments that haven't fully made the jump to native MIDI 2.0 per-note messages.
For now, the sensible approach for most MPE musicians is to keep using MPE as it exists today while watching MIDI 2.0 adoption progress in the background. The protocol transition is real, but it's playing out gradually, one profile and one transport layer at a time, rather than as a single cutover moment.