MIDI 2.0

[Rainman]

OK don't even know where to post this anymore, so many sub groups. However the new MIDI 2.0 was approved during the recent NAMM show. What ramifications do you see for your work flow, is everyone going to dash out to get new controllers/keyboards even though it's backwards compatible (to some extent). What will it mean for the future (existential question), and most importantly what do DAW designers have to tweak or overall re-code to meet this new standard? It's been 35 years since 1.0 with updates to the point where it's been exhausted. I've been following this but it seems as though the potential will still be expanding for far past when you and I will take full advantage of it.

[bayswater]

For all those looking forward to MIDI 2, my best wishes. My vote is to have the option in DAWs of staying with MIDI 1, rather than using MIDI 2 with backwards compatibility, and all the new bugs and weirdness that will involve. Of all the things that stop me from being better at making music, MIDI 1 limitations are not very high on the list.

[HCMarkus]

For all those looking forward to MIDI 2, my best wishes. My vote is to have the option in DAWs of staying with MIDI 1, rather than using MIDI 2 with backwards compatibility, and all the new bugs and weirdness that will involve. Of all the things that stop me from being better at making music, MIDI 1 limitations are not very high on the list.

+1

[monkey man]

+1 here too.

MIDI has never limited me; only I excel at that.

[MIDI Life Crisis]

MIDI has never limited me...

It's not that I haven't tried!

[mikehalloran]

What ramifications do you see for your work flow, ...

None yet. Maybe someday — perhaps never.

[Michael Canavan]

Personally I looked at the specs, looks good, MPE is included, helps DAWs get reports from plug ins, for instance it looks like virtual instruments can report their preset names to the DAW, so for instance DP and other DAWs can receive this information on a universal level. Nothing about someone becoming a better player somehow, just improvements in communication.

https://www.MIDI.org/articles-old/detai ... y-exchange

[gseibert]

32 bit values for pitch, controllers, and timing will be important to some, I think.

[richhickey]

I'm most interested in the attribute type and attribute ID in the Note On messages. This is a path to articulations on the notes, which is something DP can't do right now.

[Prime Mover]

I'm game as long as it kicks DAW maker's butts into supporting MPE. IMO, MIDI1 with MPE is not limiting, but MIDI1 without it most definitely is.

This said, I still think that MPE is bit of a "hack" to MIDI1, and should be cleaned up for MIDI2 implementation without the need for sending notes on multiple channels. To me, a channel should always be a single instrument, in a perfect world. Polytouch instruments should be able to send multiple pitchbend channels and controllers that are attached to specific notes. NOT designate each note to a different channel in order to overcome the shortcomings of the midi1 standard.

[monkey man]

Maybe they'll bundle all 16 channels into a single entity for MPE convenience, Eric? Seems like it'd be an obvious fix / development to me.

MIDI has never limited me...

It's not that I haven't tried!

[Prime Mover]

That would be a decent start. But I appreciate object models as they would behave in the physical world, where properties of a note are attached to the note event itself. 16 streams where notes are randomly thrown around to along with controller data isn't exactly a very elegant model. It's making the best use of an arbitrary construct.

Instead, how about a single stream but where each note event has its own controller data directly attached to it. That more directly models what's going on in the physical world: you have a note, it has properties, and then those properties change.

[monkey man]

I hear ya mate.

That's essentially what I meant - that ultimately the shenanigans and "details" be moved under-the-hood into a single pipeline.

[bayswater]

Wasn't all this stuff was decided a long time ago?

[Prime Mover]

I'll admit, I really need to study the MIDI2.0 spec a little more. I ran over the features, but they're open-ended enough, I have less of an idea on how they're actually going to be used in practice.

Unfortunately, I can't imagine anything but extreme resistance and disinterest by DAW developers. I'll admit, the need for extended MIDI is an incredibly niche market, and modern software companies seem incredibly focused on NOT being niche. I'd like to think MOTU hasn't adopted MPE yet because they want to wait until MIDI2 shakes out, but more likely, they don't think it's worth the trouble for all 5 of us who are going to make use of it!