Here is a link to a gearspace conversation on Midi 2.0.
Midi 2.0 will mean devices talking. Meaning they will configurate themselves. It hasn’t been finalized yet. But if you are interested. You can find the latest greatest there. Including development tools. People from Microsoft, Apple, Roland, Yamaha and many others are in that thread.
It’s a definite area of interest to a few of us. Classical composers for sure, i often use ‘14bit Midi’ as the resolution is so great, so no stepping, but it can get a bit messy in editing.
Would be rather interesting to those of us who program ‘real’ drums too for the same reasons.
Fingers crossed that it makes it into ‘main stream’ usage and production. 
Microsoft being onboard is a hopeful indicator, though.
I am not a technician in midi programming but in the current midi there are some predefined instruments in the midi code so when you output . 128 of them. But once you open up to a much higher bit depth it would allow for actual embedding more instrument detail into a midi output. So like in network packets the hardware address can be used not only to identify the card the data is going to, but also the manufacturer and model number. If using this same approach when you do a midi export of music, it can identify properly what vendor and instrument model/version etc. so this would allow for a route or language to exchange music between different DAW
Well currently I use 3 devices with usb midi. A Arturia Spark, A Keylab MKII and a Korg Taktile. It doesn’t work together. I am thus switching to a digidesign midi i/o.
So that is one thing. Then there is the expression level. And automatic recognising of devices. I allso use a Control24 mixer. Many large format mixers with automation use midi in some sort of way. Automatic configuration will be a big thing for users.
Follow us for the hottest sounds, fresh content, exclusive offers and Arturia news as it happens.