Long form: Kong has just released a new pair of keyboard controllers, called the Keystage, that implement MIDI 2.0. This includes Property Exchange and MIDI Polyphonic Expression. And the keys themselves are are quite nice (tried the 61-key model at NAMM). I want to know if GP4 is compatible with this unit.
Very interested in this thread,since I’m currently sitting on the fence about ordering the Keystage for gigging. Currently I know that in theory MIDI 2.0. allows Keystage to communicate “both ways” and read which parameters its currently controlling, thus enabling it to show on its tiny screen the names of the controls below the knobs. But I haven’t yet grasped what does this require from the plugin or plugin host side in order to work properly.
Another thing that interests me especially as a synth nerd is the knob resolution: MIDI 2.0 should enable 4 billion something steps instead of 128 like in old midi-standard. But Korg seems to be pretty quiet about the knob resolution of the Keystage, I’m assuming it could be 32 but is it? And does this again require some patching from plugin developers or will the resolution simply be higher once you start using a MIDI 2.0. enabled controller?
Not all people, and definitely not “all values”, so the jump in resolution won’t matter to most basic users of midi-gear. But I would argue that musicians who have spent significant amount of time playing and tweaking hardware synths will notice a difference in how some basic stuff like filter cutoff control responds to live tweaking (while playing a lead solo for example). While physical build-quality stuff will of course also have an effect, meaning a controller with very flimsy pots will feel flimsy no matter what the resolution, with even some pretty rugged midi-controllers (Soundforce comes to mind) the stepping in the response IS noticeable, at least if you like doing subtle dynamic stuff and tweaking with higher resonance values.
Plugins have come a very long way in emulating the sound of great analog gear and based on just recorded samples the best ones are pretty much indistinguishable from their HW counterparts, even for an expert. But put a blindfold on a seasoned synth wizard and let them do their magic with physical knobs; they will notice the difference between adjusting a MIDI CC control and adjusting an analog synth, no matter how great the plugin and how great smelling wooden panels the controller has (and I do like the SFC-5 for example, it is still a highly enjoyable little piece of gear, it’s not their fault the MIDI standard is 40+ years old).
I quess there will be many people thinking now I should consider switching snake oil to more nutritionally rich beverages. But I still think MIDI 2 is a very worthy step forward and upgrading the resolution will matter to more than just a few musicians (not even mentioning all the other upgrades in the new standard). Not that I’m not eternally amazed at and grateful for what Dave Smith and Ikutaro Kakehashi achieved; the good ol’ MIDI is impressive piece of engineering even by today’s standards. Digital gear just has progressed a lot, so why not let MIDI finally grow with it.
I’d like to know if it is, so far I can not get Gig Performer to recognize my Kontrol S88 MK3 with midi 2.0.Midi 2.0 is a Hugh step in the development of midi,Gig performer needs to get on board
I have quite mixed emotions about MIDI 2.0. I must admit that I have not had a deep dive so far (will do this around easter ). So feel free to correct any of my statments below if I tell nonsense! Just scratching the surface…
First of all - classic chicken/egg situation: only few HW / SW out in the field (Roland, NI, Korg, ???)
From my point of view there’s a lot mixed information about MIDI 1.0, MPE and MIDI 2.0
a lot of people refer to polyphonic aftertouch when talking about MPE/MIDI 2.0
poly AT was already available in MIDI 1.0, Yamaha CS-80 was one or the first device providing it. We also had great devices like the ensoniq TS-10 in the 90s and löots more later on.
MPE adds some more possibilities (which?)
MPE is an amendment to MIDI 1.0!
MIDI 2.0 is bidirectional
yes, MIDI 1.0 some kind of by USB as well
Auto config / profiles - this is the least clear part for me:
how do you initiate a profile exchange/transfer?
how long does ot take to exchange and setup?
how can you influence this as a user (take/ignore) a profile?
how could one do own profiles (e.g. to be used in a future GP version)?
MIDI over network
already there (MIDI over RTP), but not standardized by MMA. So good if this gets finally adressed in the standard!
other features
I think there’s a lot to discover - I’m really interested in this
cabling/connections could get easier if everything goes USB-C - but what about reliability?
However, I think there’s also a lot of improvement and clarification needed in the existing 1.0 universe
bidirectional communication / status exchange for LEDs, Displays is a PITA on a lot of devices (see my KeyLab MkII scripts…). It could be so simple if manufacturers would listen carefully and spenst some extra lines of code…
The item that is probably most interesting is the ability to query a synth for its parameters after which you could treat a hardware synth as if it was a plugin in terms of host automation.
But as noted, there aren’t many devices that support it yet