MIDI 1.0 tops out at 128 possible velocity values per note, a limit baked into the protocol since 1983. That's seven bits of resolution for how hard or soft every single hit gets played. Supreme Drums Nashville runs on MIDI 2.0 instead. There, the same parameter gets sixteen bits and 65,536 possible values.
Sound Magic didn't round that number for marketing. Sixty-five thousand five hundred thirty-six is the literal ceiling MIDI 2.0 allows. Supreme Drums Nashville's velocity range sits exactly at that ceiling, not some fraction of it. The MIDI Manufacturers Association only finalized that spec around 2020, after more than a decade of development work. This is a recent capability, not an old one repackaged.
Seven bits sounds like plenty, until you're layering hundreds of samples across a full dynamic range. Every recorded hit has to get rounded to the nearest of 128 steps. When two adjacent notes land in the same step, the ear catches it as banding rather than a smooth crescendo.
The MIDI Association's own documentation calls this velocity banding. It's been a known limitation since the format launched at Winter NAMM in 1983. A mezzo-forte snare hit under MIDI 1.0 sits at a single fixed value. Only a handful of neighboring values on either side count as the same dynamic marking. MIDI 2.0 gives that same marking thousands of possible values instead. That's why a slow crescendo on the snare reads as continuous rather than stepped.
One published example from the MIDI Association makes the gap concrete. Under the old format, a mezzo-forte note centers on value 79, with a working range of roughly 73 to 85. That's just thirteen possible values covering that whole dynamic marking. The MIDI 2.0 equivalent centers near 40,569, with a working range that runs from about 37,449 up to 44,209. That's close to 6,760 values sitting inside a single dynamic marking that used to have thirteen. A drummer's ghost notes and accents both live inside that same marking on a real kit. That's exactly the kind of nuance thirteen values can't hold.
The extra resolution isn't limited to velocity either. MIDI 2.0 also expands controller data from seven bits to thirty-two bits, and channel or per-note pressure gets the same upgrade. For a drum instrument, that pressure and aftertouch data can drive things like hi-hat openness. It moves in far finer steps than a MIDI 1.0 connection allows.
Piano libraries hit this ceiling first, simply because pianists cover a huge dynamic range on a single key. Drums hit it constantly too. Every part moves between a whisper and a full hit within the same bar, sometimes several times.
That fallback isn't a downgrade to nothing. Sound Magic's own documentation for Nashville lists the snare as offering up to 127 velocity layers under plain MIDI 1.0. That's the full seven-bit range the older format allows. You lose the extra headroom above 128 steps, not the instrument itself.
MIDI 2.0 also adds per-note pitch and modulation control. A single struck note can carry its own data instead of sharing one value across the whole channel. That's part of the same protocol upgrade behind Nashville's velocity range. The marketing copy only ever mentions the headline number.
Mixed setups work too. A MIDI 2.0 packet can carry an embedded MIDI 1.0 message inside it. A Nashville track routed through an older piece of hardware in the same session doesn't need a separate configuration step. The negotiation and the fallback both happen automatically, underneath whatever velocity number ends up in the plugin's marketing copy. None of that machinery shows up on a spec sheet. It's the actual reason a headline number like 65,536 turns into something a session can use, rather than a figure nobody's hardware can reach.
Sound Magic didn't round that number for marketing. Sixty-five thousand five hundred thirty-six is the literal ceiling MIDI 2.0 allows. Supreme Drums Nashville's velocity range sits exactly at that ceiling, not some fraction of it. The MIDI Manufacturers Association only finalized that spec around 2020, after more than a decade of development work. This is a recent capability, not an old one repackaged.
Seven bits sounds like plenty, until you're layering hundreds of samples across a full dynamic range. Every recorded hit has to get rounded to the nearest of 128 steps. When two adjacent notes land in the same step, the ear catches it as banding rather than a smooth crescendo.
Seven bits of resolution create audible steps
A snare roll built from soft ghost notes into a hard accent might pass through forty or fifty distinct velocity values in a few bars. Under MIDI 1.0, several of those hits get rounded into the same one of 128 available steps. Two notes that felt different under your fingers end up triggering the exact same sample layer. Under MIDI 2.0's 65,536 steps, that collision essentially stops happening. There's roughly 512 times more room between the softest and hardest possible hit.The MIDI Association's own documentation calls this velocity banding. It's been a known limitation since the format launched at Winter NAMM in 1983. A mezzo-forte snare hit under MIDI 1.0 sits at a single fixed value. Only a handful of neighboring values on either side count as the same dynamic marking. MIDI 2.0 gives that same marking thousands of possible values instead. That's why a slow crescendo on the snare reads as continuous rather than stepped.
One published example from the MIDI Association makes the gap concrete. Under the old format, a mezzo-forte note centers on value 79, with a working range of roughly 73 to 85. That's just thirteen possible values covering that whole dynamic marking. The MIDI 2.0 equivalent centers near 40,569, with a working range that runs from about 37,449 up to 44,209. That's close to 6,760 values sitting inside a single dynamic marking that used to have thirteen. A drummer's ghost notes and accents both live inside that same marking on a real kit. That's exactly the kind of nuance thirteen values can't hold.
The extra resolution isn't limited to velocity either. MIDI 2.0 also expands controller data from seven bits to thirty-two bits, and channel or per-note pressure gets the same upgrade. For a drum instrument, that pressure and aftertouch data can drive things like hi-hat openness. It moves in far finer steps than a MIDI 1.0 connection allows.
Piano libraries hit this ceiling first, simply because pianists cover a huge dynamic range on a single key. Drums hit it constantly too. Every part moves between a whisper and a full hit within the same bar, sometimes several times.
Backward compatibility happens through negotiation, not guesswork
None of this breaks older gear. MIDI 2.0 devices and hosts run a negotiation called MIDI-CI before anything else happens. That negotiation trades messages built on the old MIDI 1.0 system exclusive format to check whether both sides actually speak MIDI 2.0. If your DAW or controller only understands MIDI 1.0, Nashville falls back automatically rather than refusing to load.That fallback isn't a downgrade to nothing. Sound Magic's own documentation for Nashville lists the snare as offering up to 127 velocity layers under plain MIDI 1.0. That's the full seven-bit range the older format allows. You lose the extra headroom above 128 steps, not the instrument itself.
MIDI 2.0 also adds per-note pitch and modulation control. A single struck note can carry its own data instead of sharing one value across the whole channel. That's part of the same protocol upgrade behind Nashville's velocity range. The marketing copy only ever mentions the headline number.
Mixed setups work too. A MIDI 2.0 packet can carry an embedded MIDI 1.0 message inside it. A Nashville track routed through an older piece of hardware in the same session doesn't need a separate configuration step. The negotiation and the fallback both happen automatically, underneath whatever velocity number ends up in the plugin's marketing copy. None of that machinery shows up on a spec sheet. It's the actual reason a headline number like 65,536 turns into something a session can use, rather than a figure nobody's hardware can reach.
