MIDI 2.0 gets talked about in the same breath as MPE often enough that it’s easy to assume it’s the same thing with a version bump. It isn’t. MPE is a clever workaround built entirely inside MIDI 1.0’s limitations — channel-per-note tricks to fake per-note expression on a protocol that was never designed for it. MIDI 2.0 is a different, backwards-compatible protocol that removes the need for the workaround in the first place, while still being able to fall back to 1.0 for any device that doesn’t support it.
The feature to learn first: Property Exchange
Before getting into resolution numbers, the one MIDI 2.0 feature that changes daily workflow is Property Exchange (part of MIDI-CI, Capability Inquiry) — a handshake where a controller and a synth introduce themselves to each other over MIDI. Instead of you opening a manual to find out that CC 74 controls filter cutoff on this particular synth, a MIDI 2.0 device can query the other device and receive back a list of what it actually has: its name, its available controllers, what each one is called, its current state.
Practically, this is what lets a MIDI 2.0 controller auto-label its knobs to match whatever synth is plugged in, instead of shipping with a fixed CC map and a lookup table of presets for popular gear. The handshake happens automatically on connection — nothing to configure, but worth knowing it’s the reason newer MIDI 2.0 gear can “just know” what it’s talking to.
What actually changed under the hood
- 32-bit controller resolution, up from MIDI 1.0’s 7-bit (128 steps) or the 14-bit tricks used to combine two CCs. A filter sweep that used to step audibly now has headroom to be smooth.
- Per-note controllers are native, not simulated. MIDI 2.0 can send pitch, pressure, and other per-note data on a single channel without needing MPE’s channel-allocation trick — the capability MPE existed to approximate is built in.
- Registered and Assignable Per-Note Controllers let a device expose named per-note parameters (not just pitch and pressure) that a controller can discover via Property Exchange rather than guess at.
- Jitter reduction timestamps improve timing precision for sequenced and networked MIDI, relevant mostly for complex multi-device rigs rather than a single synth and controller.
Where it actually runs today
MIDI 2.0 requires both ends of a connection to support it — a MIDI 2.0 controller talking to a MIDI 1.0-only synth automatically negotiates down to 1.0 during the Capability Inquiry handshake, so nothing breaks, but nothing new is gained either. Native support is strongest over USB (where it was first standardized) and increasingly over Bluetooth LE MIDI and network MIDI; 5-pin DIN MIDI can carry MIDI 2.0 data but adoption there is slower, since most hardware using the 5-pin jack predates the spec.
Where to start if you own MPE gear already
If you’re already using an MPE controller, you’re using the thing MIDI 2.0 was partly designed to make unnecessary — which means the practical first step isn’t replacing anything, it’s checking whether your synth or DAW’s MIDI 2.0 support is enabled by default or needs to be turned on in a settings menu, since several hosts still default new projects to 1.0 for compatibility.