Windows 11 - Windows MIDI Services gets retail release (24H2/25H2)

[Vocalpoint]

See more here:

About Windows MIDI Services

Microsoft Windows MIDI Services API, SDK, and tools

microsoft.github.io

This page also features a new service checker that will let you know if the new feature is available and active:

Not for me as of yet

KB 5074105 will enable the new backbone (wdmaud2.drv) and will significantly up the game for MIDI on Windows:

• No need for third-party USB drivers in most cases. Most USB MIDI 1.0 devices are class-compliant and will work without third-party drivers. This means no wrestling with their position in the registry, or worrying about compatibility. Don’t install third-party drivers unless absolutely necessary, and you’ll have a better MIDI experience on Windows.
• Supports your Existing Apps. The existing WinMM and WinRT MIDI 1.0 APIs have been repointed to the new Windows Service. This provides a subset of the new features, including multi-client so your apps will continue to work as today, but will be even better.
• Multi-client by default. Any endpoint (including MIDI 1.0 devices) can be used by multiple applications at the same time. That means you can use a librarian or controller app at the same time your DAW has a connection open.
• Supports your Existing Devices. Windows MIDI Services supports the MIDI 1.0 devices you own today, including those with vendor-supplied kernel streaming drivers, as well as class-compliant MIDI 1.0 and MIDI 2.0 devices. The experience will be better/faster if they use the new class driver, but we recognize that is not always possible or desirable with some existing devices.
• Faster. In our testing, we’ve found that the new infrastructure is much faster at sending and receiving messages compared to the older API, even with plugins configured in the service. There are no built-in speed caps or throttling in Windows MIDI Services, even for older USB MIDI 1.0 devices. The new MIDI 2.0 driver is not limited USB full-speed, and supports USB 3.x speeds.
• Lower Jitter. Along with higher speed comes lower jitter. This will vary by transport type (USB vs Network vs Virtual), and the device Windows is talking to, but the jitter is in the low microsecond range even without any compensation.
• More Deterministic. Speaking of latency compensation, the new API enables timestamp-based message scheduling for outbound messages for any apps using the new API. In addition, incoming messages are tagged with a timestamp when received by the service.
• App-to-App and Virtual Device MIDI. Windows MIDI Services includes built-in virtual / app-to-app MIDI 2.0 to enable lightning fast communication between apps on the PC.
• Better tools. We supply the midi.exe Windows MIDI Services Console for developers and power users, or anyone comfortable with the command line. You can use it to monitor endpoints, send and receive messages, send/capture SysEx data and much more. We also include the MIDI Settings GUI app for renaming devices, configuring your MIDI setup, testing, and more.
• Built-in Scripting Built-in support for scripting MIDI using PowerShell. Want to automate synchronization between mixers? Want to set up a script to initialize all your devices for a show? All this can be done via the PowerShell Cmdlets.

Have fun out there.

VP

 

[John Vere]

I guess we will find out.
I did an extensive test of midi latency a few years ago and I still have all that. I made a video about it but it wasn’t a hot topic so I eventually deleted it. I still have the original.

The most interesting part was testing a bunch of different controllers. If they came with a midi driver from the manufacturer, Roland. Yamaha, Korg they would have very low latency. But the ones that used the generic midi driver were more than double.
So will be interesting to see.

It’s super easy to test midi latency.
Use a new project and add a midi track and an audio track.
The midi track obviously is going to record the controller.
The audio track place a Mike about 1” from the keys.
Start recording both tracks and hit the key hard enough that the Mike gets a good signal.

Now observe how long it took for the midi note to start as compared to the audio.

You need to be using a proper audio interface and ASIO. Its timing is hopefully accurate down to the sample level.
Midi 1.0 transmission is said to be around 1 ms average. But that would be using 5 pin from hardware to hardware.
Toss in a computer USB system and it will start adding up. Midi 2.0 was supposed to make it better. Sort of like going from MME to ASIO

 

[sintil8]

Just a couple of the bullet points.
I'm looking at this and thinking 3rd party Midi inserts?

App-to-App and Virtual Device MIDI. Windows MIDI Services includes built-in virtual / app-to-app MIDI 2.0 to enable lightning fast communication between apps on the PC.

And, usb 3x speed, I would think both your Mobo and Ext. hardware need suitable ports to be capable of usb x3 speeds ?

Faster. In our testing, we’ve found that the new infrastructure is much faster at sending and receiving messages compared to the older API, even with plugins configured in the service. There are no built-in speed caps or throttling in Windows MIDI Services, even for older USB MIDI 1.0 devices. The new MIDI 2.0 driver is not limited USB full-speed, and supports USB 3.x speeds.


I look forward to Midi 2. Maybe it's time for the guys in the kitchen to start bringing some of this to the table.

Go, squeeze the wheeze! Many people like to.

Kindest regards

 

[TheMaartian]

Maybe this doesn't run on Win11 Pro? If I just double-click on the .EXE, an outline of a window flashes and then exits. If I run the .EXE as an admin, I get the UAC pop-up. After clicking on "Yes", it exits to the desktop. Disabling my VPN made no difference.

 

[sintil8]

Maybe this doesn't run on Win11 Pro? If I just double-click on the .EXE, an outline of a window flashes and then exits. If I run the .EXE as an admin, I get the UAC pop-up. After clicking on "Yes", it exits to the desktop. Disabling my VPN made no difference.

Yeah, that is what I'm getting?
I have not yet installed the latest KB update and thought, maybe it needed that update for it to work?
I read some of the support stuff and there is something about allowing Midi 2 services through on the firewall side.
Looks like time reading up on this, as I do not have an answer myself?

Kindest regards

 

[Vocalpoint]

Maybe this doesn't run on Win11 Pro? If I just double-click on the .EXE, an outline of a window flashes and then exits. If I run the .EXE as an admin, I get the UAC pop-up. After clicking on "Yes", it exits to the desktop. Disabling my VPN made no difference.

This is a command line tool. You cannot run it straight up. Open a CMD prompt and run it.

And yes - you can run this tool on any Win 11 install - but your install must have KB 5074105 (or later) to get the new package.

Tested (and confirmed) this over the weekend.

VP

 

[sintil8]

This is a command line tool. You cannot run it straight up. Open a CMD prompt and run it.

And yes - you can run this tool on any Win 11 install - but your install must have KB 5074105 (or later) to get the new package.

Tested (and confirmed) this over the weekend.

VP

Yes I am getting the same. "Not present in registry..."
Dropped the downloaded file into an open Command prompt window sorted it. Cheers VP.

Kindest regards

 

[TheMaartian]

This is a command line tool. You cannot run it straight up. Open a CMD prompt and run it.

And yes - you can run this tool on any Win 11 install - but your install must have KB 5074105 (or later) to get the new package.

Tested (and confirmed) this over the weekend.

VP

Thanks. And, no, I don't have it yet.

EDIT: I opened Windows Update to see if 5074105 had been installed. Lo, and behold, there it was, waiting to be downloaded and installed. Downloading now. Getting there.