Anyone who has written orchestral parts in a DAW knows the keyswitch routine: a low note chooses spiccato, another chooses tremolo, and the piano roll fills up with markers that are not really music. The MIDI Association has a proposed fix in MIDI 2.0, and it sits alongside MPE rather than replacing it. Understanding the difference helps you choose the right tool for each part of an expressive workflow.
What the profile does
In the MIDI Association's February 2026 status update on MIDI 2.0, the Orchestral Articulation profile (M2-123) is listed among the finalized Profile documents. Instead of using keyswitch notes, it encodes articulation in the attribute fields of the Note On message. It covers eight instrument categories, so a sequencer or notation program can tell a compatible sample library which articulation to use for each individual note.
Profiles are negotiated through MIDI-CI: one device inquires, the other reports what it supports, and the profile is switched on. Once enabled, both sides agree on the meaning of the data, so you do not need a custom keyswitch map for every library.
How that differs from MPE
MPE and the articulation profile solve different halves of the expressive problem.
MPE is about continuous gesture. Each note gets its own channel, so pitch bend, pressure and slide (CC74) can move independently while the note sounds. It works over standard MIDI 1.0 connections and is supported by many controllers, plugins and DAWs today.
The articulation profile is about discrete choice. It labels a note with a playing style at the moment it starts. It does not describe how the note evolves afterwards. A legato violin line still benefits from vibrato depth under your finger, and that is MPE territory.
In practice an ideal orchestral part could use both: articulation chosen per note through the profile, with dynamics and vibrato shaped through per-note pressure and slide.
Where it stands today
It is important to be realistic. The status update confirms the specification is finalized, but it does not list specific DAWs or sample libraries that ship with support, and it notes that true high-resolution messages may depend on operating system and endpoint support. It also describes work by Apple, Avid, Bitwig and Steinberg, with JUCE involved, on an open-source MIDI-CI Helper that translates Profile messages into native plugin formats. That is the kind of plumbing that has to arrive before plugin developers can adopt the profile widely.
The update mentions MPE only in passing, and it does not describe an MPE profile or a formal link between the two. So the combination described above is a way of thinking about the workflow, not a documented feature.
What this means for your setup
For now, nothing about your MPE rig needs to change. A few practical points:
- Keep using MPE for expression. Controllers such as the Expressive E Osmose, LinnStrument and ROLI Seaboard work with the plugins and DAWs you already have.
- Watch library announcements. If a developer of orchestral instruments mentions M2-123 or MIDI-CI profile negotiation, that is your signal that keyswitch-free articulation is becoming real.
- Check your DAW's roadmap. The profile needs a host that can negotiate MIDI-CI and pass attribute data through to the plugin. Look for explicit MIDI 2.0 support in release notes rather than assuming it.
- Do not abandon keyswitches yet. They remain the practical standard across libraries and will for some time.
The bigger picture
The Orchestral Articulation profile shows where MIDI 2.0 is heading: more meaning carried by the note itself, less by workaround. MPE showed that per-note expression was possible within the old protocol, and many of the ideas behind it, such as treating each note as its own expressive voice, appear again in MIDI 2.0's per-note controllers. The two will likely coexist for years, and expressive composers will be best served by knowing what each one is good at.
Sources: MIDI Association.