By "long way out" I mean
production level ready in Windows. NOT availability on a keyboard in the real world and not on the DEV bench of plugin or DAW maker either.
Apple tried this with Sequoia and now Tahoe and Logic (claiming full support) and if you turn MIDI 2.0 on in there - even with a (so-called fully supported) Native Instruments MKIII S61 connected - nothing works - or it crashes or any number of other weirdness pops up.
Like this for example (Oct 2025)
Using s88 and noticed it has a 2.0 option. Switched, rebooted, deleted midi controls and the keys won't produce sound in either Logic or Ableton. Switch back to 1.0 and they work again. Apple says they're compliant. NI says they're compliant. I don't know who to to trust but one of you is wrong...
community.native-instruments.com
This is key part - right from NI themselves:
"The current blocker for MIDI 2 adoption in the context of a DAW is in the plugin APIs… Apple and Steinberg are actively working on adding MIDI 2.0 capability enquiry features to the plugin APIs. There are also various other DAW profiles that we are working on with the MMA, but these likely won't see widespread DAW support for a number of years"
There is so much that has to fall into place to deliver a complete (stable) solution - it's not even a conversation yet.
I mean let's be real - Presonus doesn't even support the new v2.0 firmware on a MKIII board yet - there is a lot of small fruit to pick well before tackling something as big as MIDI 2.0
Presonus would be very smart to wait until the two major OS's
that will support this - support it with full stability and reliability - before getting crazy and rushing it.
VP