You will never understand how much work I put into preempting this MIDI 2.0 update with something modern. Nonetheless, it's what we have and it does improve things. Two-way communication and function discoverability alone is worth the change. Plug in controller, controller reports what controls it has (endless encoder, XYZ pad, etc.), plugins report what they have, connect them and allow controller to display parameter it is controlling. Pretty simple shit, should have been added 20 years ago.
I realize it's worse than a chicken-and-egg problem, given there's at least multiple, not 2, things in the ecosystem that need to magically change simultaneously. Communication protocol, hardware, DAWs, plugin standard and various other things trailing off of all of those. I once architected a replacement to all of this and made more progress than you'd expect securing the future of music-making for future generations, but ultimately lost all of the RnD. Fun times.
Nonetheless, this particular video is rather exciting as MS Research is chock full of interesting and crazy thing. You should have seen their Surface table/room prior to it becoming a tablet.
AI Text-To-MIDI:
https://www.midi.org/midi-articles/micr ... ecoco-midi
on the topic of MIDI 2.0...
-
- KVRAF
- 10286 posts since 17 Sep, 2004 from Austin, TX
-
- KVRAF
- Topic Starter
- 10286 posts since 17 Sep, 2004 from Austin, TX
https://www.kvraudio.com/news/bremmers- ... udio-58816
Bremmers Audio Design has updated MultitrackStudio to v10.7 and MultitrackStudio for iPad to v4.8.2 which support MIDI-CI. MIDI-CI is part of MIDI 2.0, it allows a sender to receive information from a receiver, which is something MIDI couldn't do until now.
The new MultitrackStudio releases use MIDI-CI to retrieve program names and controller names from a destination. This currently works with USB MIDI 2.0 class compliant devices in macOS 14 and iPadOS 17. The feature is enabled by default. All you have to do is connect the device and select it, and MultitrackStudio automatically knows about the programs and controllers the device supports.
The program and controllers names appear in lists and editors where appropriate. The feature also allows for a device to report which controllers are supported for the current program, so MultitrackStudio can present a list of controllers that actually work.
Bremmers Audio Design expects to add this feature to the Windows version of MultitrackStudio too once the Windows MIDI Services become available.
-
- KVRAF
- Topic Starter
- 10286 posts since 17 Sep, 2004 from Austin, TX
Finally a little bit of news from the MIDI manufacturer association there.
Windows MIDI 2.0 driver
https://devblogs.microsoft.com/windows- ... -the-repo/
It's really odd to watch this update slo-mo into existence after all these years
-
- KVRAF
- Topic Starter
- 10286 posts since 17 Sep, 2004 from Austin, TX
https://github.com/microsoft/MIDI/releases
Yes, I really go searching for MIDI 2.0 news once a week.
Interesting that ARM 64 is supported:
"Everything is built for both Arm64 and x64 starting with this release. Arm64 builds are supported only on the latest Windows 11"
these changes caught my eye:
Dirty-disconnect cleanup
Automatic endpoint reconnection through API
There's also this exceptionally good news:
"When discussing the delivery approaches with the API review team, we jointly concluded that the WinRT MIDI2 Application API itself should be shipped out of band from Windows rather than as part of the Windows SDK. The primary reason for this is the release and update schedules for the Windows SDK are too sparse for this product, we'd have challenges trying to make the API available to down-level Windows 10, and we'd also have to have Day 1 support for platforms that we don't tend to initially support (x86-32, Xbox, Hololens, etc.)."
Sickens me that "Day 1" hasn't arrived, with this chicken-and-egg-and-chicken issue of drivers, plugins, DAWs, and various hardware controllers all somehow magically needing to adopt MIDI 2.0 one would think that least the freaking OS support would already exist. It does for iOS and Linux, already, obviously.
Yes, I really go searching for MIDI 2.0 news once a week.
Interesting that ARM 64 is supported:
"Everything is built for both Arm64 and x64 starting with this release. Arm64 builds are supported only on the latest Windows 11"
these changes caught my eye:
Dirty-disconnect cleanup
Automatic endpoint reconnection through API
There's also this exceptionally good news:
"When discussing the delivery approaches with the API review team, we jointly concluded that the WinRT MIDI2 Application API itself should be shipped out of band from Windows rather than as part of the Windows SDK. The primary reason for this is the release and update schedules for the Windows SDK are too sparse for this product, we'd have challenges trying to make the API available to down-level Windows 10, and we'd also have to have Day 1 support for platforms that we don't tend to initially support (x86-32, Xbox, Hololens, etc.)."
Sickens me that "Day 1" hasn't arrived, with this chicken-and-egg-and-chicken issue of drivers, plugins, DAWs, and various hardware controllers all somehow magically needing to adopt MIDI 2.0 one would think that least the freaking OS support would already exist. It does for iOS and Linux, already, obviously.
-
- KVRAF
- 16806 posts since 8 Mar, 2005 from Utrecht, Holland
Linux support you say? That greatly depends on what flavour of linux you use me thinks...
We are the KVR collective. Resistance is futile. You will be assimilated. 
My MusicCalc is served over https!!
My MusicCalc is served over https!!
-
- KVRAF
- Topic Starter
- 10286 posts since 17 Sep, 2004 from Austin, TX
Announcing: Windows MIDI Services Customer Preview 1!
https://devblogs.microsoft.com/windows- ... 6_readmore
https://devblogs.microsoft.com/windows- ... 6_readmore