While I concede that you were right about the MIDI 2 rollout amongst the likes of big players like Apple, Windows, NI, Cubase, FSP, etc taking a while to sort out, it does really matter that FSP is again the last in line and has shown zero willingness to step up the pace. Microsoft is working out the kinks as far as Win11 and MIDI 2 goes; there have already been several iterations and they're serious about working out the stability issues. Looks like things are already really close on the Cubase side. Hope for your sake you're right about being able to use your mk3 KK with FSP in a few months. The ract remains FSP has not covered itself in glory by remaining mum and moveless on MIDI 2. You're allowed to remain disinterested in MIDI2; does that mean no one else should be when the likes of every major and minor entity in the MIDI Association feels differently?Doesn't really matter as the only DAWs that support MIDI 2 (if you can even call it that at this time) are Logic, Cubase, and "Bremmers" MultitrackStudio.
Until Studio Pro can boast full battle-tested MIDI 2 support for at least 2 full years - AND any keyboard controller I might choose to interface with it - has also had that same track record - then I might take a look. Until then MIDI 1 continues to be just fine.
On that note - saw another post from NI earlier today - where the guy (Tim Rae) who oversees the S-Series had this tidbit:
View attachment 3444
Good enough for me to keep my S-Series MKIII in its box for a few more months.
At least if/when SP supports the new v2.14 firmware.
VP