MIDI Windows Service rollout - Dorico implications?

Dorico and MIDI has always been problematic - not Dorico’s fault but Windows. Finally Microsoft is putting MIDI into the core system

How/when will this play with Dorico? I’ve got it already on my computer. Is there anything Dorico needs to do to take advantage of this? I see the ports already in Dorico

Is there anything I need to do to get more reliable MIDI?

Answering my own questions here after some research and testing …

Yes this is a 64bit multiclient core Microsoft provided MIDI services. So now we can have a single source multi client transparent MIDI usage like on Macs, yay! Some notes …

The old Korg stuff can be problematic. The USB drivers are no longer needed, Korg has posted a bulletin about this, go ahead (if you have them) and uninstall.

Korg BLE/Bluetooth is a problem. They plan on adding BLE MIDI to the system eventually, but if you’re using the Korg driver you can continue to use it, however it is working in parallel and not with the new system. Just make sure it’s not messing up the registry, when you install the new Windows MIDI system tools they have a button you can hit to make sure that’s fixed.

Or, if you want to have something that plays with the new multi-client/more robust, then you can uninstall the Korg BLE driver. Check the Discord for instructions. Then in the meantime you need to get the CME WIDI Bud device for $69. This is an ‘auto-magic’ MIDI BLE device. It just sniffs out devices trying to connect and does it automatically. Then it just looks like a regular USB MIDI device and works as part of the system, no problem. I happen to have this device trying to get Bluetooth MIDI working with my laptop and it solves this nicely. Eventually when they add BLE MIDI to the core I can drop it.

So far working well, no MIDI lockups like before with the XKey 37 BLE, now trying with my Doepfer using the CME WIDI Master (should be fine since it’s CME to CME)

OK, WIDI Master from a random keyboard (Doepfer) works great directly to an iPad native BT, and to WIDI Bud USB dongle to Windows. This is routing through the new native MIDI services from Microsoft.

To any app other than Dorico, such as Nuendo or Ivory Standalone, it works perfectly with low latency. To Dorico I’m getting unacceptable latency.

@Ulf any thoughts on this? Dorico can see the new Service as shown in the first post (the loopback MIDI’s using the new naming syntax), and it picks up the MIDI just fine, but just with a lot of latency.

That might be very helpful to me! I’ve been using CME WIDI with my Akai EWI-5000 for a while (very happy with it) and they recently upgraded the firmware to reduce the latency even more. (TBH, I wasn’t having any issues prior to the upgrade!)
— Jim

Hi @DanMcL , no, sorry, I have no experience, yet, with the new MIDI service.

Yeah I upgraded the firmware from iOS on both devices. So you use the WIDI Master with the Akai to give it BT? Then connect it how to where?

I have an old iConnectivity mio4 that I have a couple sound modules, An FCB-1010 (with UnO2) and the “receiving” WIDI Master plugged in. But It will also BT directly to an iPad (and, I think, my Mac Mini). I have it set for a static group so that it stays where it belongs!
I use Dorico to make charts and AM SWAM & Camelot for playing with the FCB (and TouchPortal on iPad) for remote control. :wink:

OK, heads up then it’s possible Dorico might have an latency issue with the new Windows MIDI system. This is USB MIDI as the dongle hides that its coming over Bluetooth. It’s worrysome that a USB MIDI signal has this much latency with Dorico, as this is rolled out to all Windows 11.

I’m traveling but I think I can borrow a Steinberg audio interface to see if there’s an issue there too.

I have a Win11 setup with Dorico as well. Is there something I could check for you? (The CME has been working fine with that, but I can try something else….)

Yes if you wanted to test the new system that would be great we can compare notes. If you’re Win11 is up to date you should have the service already, here is are the tools and such which are very useful

Nuendo and other are playing fine but Dorico is having trouble. Latency yesterday, this morning it’s not seeing the WIDI Bud device which is just enumerating as a generic USB audio interface. The device shows up normally in Device Manager and Nuendo is working with it. Why is Dorico having such trouble with MIDI?

Edit: Dorico required a full computer reboot to start recognizing the generic audio interface again.

Win11 25h; downloaded the tools and restarted.
What am I looking for? Device setup still shows ASIO4ALL – have a Yamaha DG-650 attached via USB. It responds pretty quickly for note input. (Switched to Steinberg - same results.) Midi interface is off and no other midi is connected.

Run the utility and start the service. Check your ports, you should have two new loopbacks “Default App Loopback” A and B. In the registry you can also check certain values are routing the MIDI. Join the Discord in the link I provided above and you’ll find getting started stuff

OK a neat trick and workaround. Since Dorico is having MIDI problems (always had problems across many computers in my experience unfortunately) but Nuendo is more stable, using the new app to app MIDI channels I’m using a MIDI track in Nuendo to forward to Dorico over one of the default MIDI loopbacks. Working great. Previously you’d have to run intermediate apps to do this kind of thing but now its built in.