MIDI 2.0 in Win 11

[asktoby]

Not sure what the implications are for Scope yet but seems cool:
https://blogs.windows.com/windowsexperi ... indows-11/

[cortone]

The latest Win11 update enables the MIDI 2.0 service. If you want to check if it is enabled on your system, a tool is available at the link below. The update does not include the actual applications, so scroll down further to get the runtime and other apps.

The short-term benefit may be the compatibility with MIDI 1.0. There is a great effort to tighten up timing for both specs, including over USB and network protocols.

https://microsoft.github.io/MIDI/get-latest/

It's still a work in progress, but a lot of effort in conjunction with the Midi Association seems to be paying off.

[Bud Weiser]

https://vi-control.net/community/thread ... st-5838629

https://devblogs.microsoft.com/windows- ... rkarounds/

Well,- seems to be a real "game changer" because it changes everything working before.
A friend of mine, using KORG and AKAI USB controllers is suffering from USB devices not recognized in Cubase anymore and devices not being migrated etc..
All came w/ latest MS Win11 update.

Seems, the existing 3rd party drivers clash w/ the new Microsoft MIDI drivers.
I wonder what will happen when MS introduces their own ASIO driver ...



Bud

[spacef]

I wonder what will happen when MS introduces their own ASIO driver ...

I think that those are for ARM first, not x86.... fortunately.
but I think x86 will follow. I don't think the ASIO will be multiclient on either plateform.

[valis]

I did a write up on all of this that I posted on Facebook under the scope community. There are potential issues with current mid loop back adapters. I will come back and post the fix, it’s fairly simple.

[cortone]

Bummer, lost a post somehow!

There are reports of "no problems" as well. It will take a couple of weeks to understand how widespread the issues are.

The workarounds do look straightforward, it's worth checking the options. The fastest fix may be to roll the update back and wait for things to settle out.

Always check before updating production systems!

MS is developing these OS services to accomodate MIDI 2.0 in conjunction with the Midi Association. Good on all the players for trying to make things backwards compatible and to fix longstanding 1.0 challenges in Windows. This would be much easier if they didn't bother. It's easy to blame MS for problems, but the vendors have a role too, and often miss on protocols and compatibility.

MS would only spend resources on ASIO if Steinberg or ASIO4all asked them to, which is unlikely.

[valis]

The issues with midi loopback are both API and signed driver related, and to fix it you first have to ensure the driver is 'below the 10 device limit' even though the new API addresses that, and to get the older driver(s) to appear once you know they are within the first 10 listed, just open an elevated (admin) command prompt and do:

Code: Select all

net stop midisrv
net start midisrv

Here's the full article I posted on facebook and X for all changes we will see, including the MIDI 2.0 which is already out:

https://www.facebook.com/share/p/18CfzTCrbM/

https://x.com/beyond_teapots/status/201 ... 34649?s=20