Midi 2.0 incoming ?
Hi there ! can someone please explain to me what's going to happen?

 

It's coming in the future.

 

‎

 

Last edited by a moderator: Jul 19, 2025

Thanks for the info.

 

Last edited: Feb 12, 2019

maybe in the near future a triangle library will weigh a terabyte

 

Member companies are currently working together to develop prototypes based on a jointly developed, feature-complete, draft specification. The is a members-only ‘plugfest’ planned for NAM 2019 to test compatibility between some early MIDI 2.0 prototypes. Participating companies include Ableton/Cycling '74, Art+Logic, Bome Software, Google, imitone, Native Instruments, Roland, ROLI, Steinberg, TouchKeys, and Yamaha.

Having established the core features of MIDI 2.0 the 2 associations will be continuing to work with their member companies to to undertake the prototyping phase as well as the development of a MIDI 2.0 logo and self-certification program for MMA and AMEI member companies.

The MIDI 2.0 initiative will update MIDI with auto-configuration, new DAW/web integrations, extended resolution, increased expressiveness, and tighter timing, all whilst maintaining a high priority on backward compatibility. This major update of MIDI has been designed to pave the way for a new generation of advanced interconnected MIDI devices, while still preserving interoperability with the millions of existing MIDI 1.0 devices. One of the core goals of the MIDI 2.0 initiative is to also enhance the MIDI 1.0 feature set whenever possible.



Is The MIDI 2.0 Spec Available?
During the prototyping phase, the proposed MIDI 2.0 specification will only be available to MMA and AMEI members, as the prototyping process may trigger minor enhancements to the specification. Once a final specification is adopted, it will join the current MIDI specifications as a free download on the https://www.midi.org

https://www.midi.org/articles-old/t...industry-amei-announce-midi-2-0tm-prototyping

 

Nah correct me if im wrong, but midi 2.0 will be integrated in midi controllers, i dont think vst libraries will be changed all that much if at all! (Besides velocity of course)

 

Last edited: Feb 12, 2019

i was joking , Hoppe was talking about many more velocity values and so many more samples

 

We'll have 10TB+ piano sample libraries with 65536 velocity layers. One step closer to decent realism...

Spitfire will launch the same libraries with 4x the size and different names.
8dio too, multi-grammy awarded Trolls Foelman will suffer a cardiac arrest for signing too many pointless 8dio stuff and he'll leave us.

And many more cool useful things.. especially cool...

 

Last edited: Feb 12, 2019

Changed to "industry news" section. "Forum News" section is for information about this forum.

 

my humble thoughts:
1) MPE (=MIDI Polyphonic Expression) needs to be properly incorporated and defined into MIDI as a standard
2) DAW control capabilities need to be severely refined and updated
3) core functionality of MIDI (channels range, program change, control change, value ranges etc..) need to be adjusted to meet nowadays standards (for ex. let's say average motorized fader can output 1024, but midi value can be 0-127 only, so severe degradation of resolution)
4) defined new class compliant (=no additional manufacturer driver required) for fresh new MIDI capable devices

 

I think MPE and higher than 7 bit resolution are already included. But we'll have to wait how they implement it in practice. I don't know how benefits it will bring to us computer musicians but I'm looking forward to.

If you think about it, a jurassic (early 80s tops?) hardware protocol has brought us a lot of cool things. The modern MIDI v2 will logically have more in mind "soft only" possibilities, implicitly or explicitly.

 

Haha I wonder though, do we really need that many velocity layers!? That's a big decision they are going to have to make whether or not they want to sacrifice that much space.

 

Well, obviously I was joking, but there're things they might benefit of better resolution. It makes more sense in the case of a synth actually. You're generating the sounds so it's not a problem to generate whatever velocity value you want from it. In case the synth is velocity sensitive, that is.

If you're using a hardware MIDI keyboard/surface you don't know what instrument/control you're playing. So it really matters to hardware developers too.

And perhaps something we barely use as MIDI CC automation could really use more than velocity..

But even if we think in the most used MIDI controls, let's say Pitch Bend. For me it's enough to have only 128 values. But pitch bend has negative and positive values. That means that there's no "standard" zero value, which is important because it's the default one.

So MIDI developers typically use either 63 or 64 for "zero value". 0 would mean full pitch bend down, 127 full pitch bend up. That matters to MIDI developers, because there's no standard for that, just the 64 (or 63) as a de-facto standard.

A proper MIDI API should be able to tell the developer which value is the zero. If they decide to use a floating point value then there's no need.

 

hadn't yet considered this +1

..furthermore roli is just the tip of the iceberg for the 'expressive controllers' we'll see

 

Hans Zimmer Pianos 2 with 4 Billion velocity layers. HDD space needed, 45 Petabytes :D

 

It was a hard choice to vote this "funny" or "agree"

 

The day a sample library is actually heavier than the actual instrument

 

I am very excited about MIDI 2.0, specially in regards to the jaw-dropping 32-bit resolution, which means 4,294,967,296 different velocity values audacity find my iphone origin (I'm not kidding). My main concern is the CPU usage for samplers using this technology, if with 7-bit resolution (127 velocity values), sometimes our CPUs struggle with multiple Kontakt instances, what about 32-bit? There better be some godamn revolutionary optimization in MIDI 2.0.

 

Last edited: Jul 19, 2019

=) I think this is too accurate a statement to not be lauded by everyone, fans especially! I anxiously await Paul Thompson proudly trumpet Spitfire's latest MIDI2 compatible library ("Silence") with 10,000 mic positions (including the ISS, nearby asteroids) and patented zero velocity layers. "We've curated infinite possibilities!"

Yeah, they really need to sort out automation too so it is kinda omni and can be switched to any like CC or w/e. It has some weird special status that is a PITA, needs to be "extracted", c/p etcs. And never just works. Pitch bend is just messed up and seems to decide values (like x00 or x0000) at random depending on how windy it is outside. Just a messy chore translating all this stuff that's like it is... because reasons?