MIDI 2.0
UMP packs messages into 32-bit words, raising velocity to 16 bits and controllers to 32.
Related
Seven bits give only 128 steps, so a long slide shows stairs and a fine filter sweep cannot be drawn. MIDI 2.0 fixes resolution first, then how devices talk.
The problem
Pitch bend uses 14 bits, yet controllers still stop at 0 to 127. Sixteen channels run short once MPE is on. Old and new gear also need rules for fallback and negotiation.
Protocol or message
MIDI 2.0 arrived in 2020 around UMP, where each message occupies one or more 32-bit words. Channel Voice velocity rises to 16 bits, controllers to 32, and pitch bend widens too. MIDI 1.0 messages remain as a compatibility layer. The two sides exchange capability inquiries and negotiate a protocol. Property Exchange describes device abilities in JSON, while Profiles declare behaviour.
Settings and practice
Let the system negotiate when old and new gear meet, rather than forcing a mode. Keep MIDI 1.0 as the export floor so a receiver can fall back. Make high-resolution controllers carry real data, not padded 7-bit values.
What to listen for
Slow slides are smoother, soft playing has finer steps, and filter sweeps lose their staircase. The gain is clearest in small movements, while large gestures hide it.
Common misunderstandings
MIDI 2.0 is not a new connector, since DIN and USB both carry it. It is not an audio protocol. UMP is not a file format, and SMF remains a separate container.
Listen in the library
All tracks from midicn-lib — inline badge is the license tier (C1 commercial / C2 non-commercial / C3 study only).
Sources
- MIDI 2.0 规范对 UMP、能力询问与协议协商的定义，依 MMA 公开规范核查，未抄文本
- MIDI 2.0 与 MIDI 1.0 的兼容层设计，依公开技术说明核查，未抄文本
Used for fact-checking only; all prose is original.