Right now, there’s nothing you can do. I traced the fault to something internal in those drivers. I’ve reached out to inMusic to see if there’s something that can be done.
Those drivers have always crashed (I validated that yesterday on a PC without the new MIDI stack), except it could be ignored due to it being only in the app (direct connection to driver) vs the new setup with a service in between.
We’re looking to see if there’s any way we can protect the service from these, but it’s not a short-term fix.
As noted in the sticky, see Windows MIDI / Audio and #start-here for other options.
Hi Pete - I better changed my MIDISPORT 2x2 and 4x4 (the older verzions - as in your picture) for their Anniversary eddition so I am sure all the problems are lost as soon as the interfacess arrive (during next week).
I hope I remember to write back just the confirmation of it
The bug is the inMusic driver, not the device. No matter what device you use, it will crash.
It does this today, but you likely don’t notice like apps hanging open in task manager. Or in the case of a REAPER user, realizing they had to unplug their keyboard and move it to a different USB port each time over the years.
My Midisport 2x2 seems to be working. I uninstalled the M-Audio drivers and Windows recognized the MIDI interface.
The port names are now different.
I have a problem with my Korg Monologue. I uninstalled the Korg driver yesterday. The Monologue was recognized, but it doesn’t run very stably with the Microsoft driver. The Monologue froze several times in Cubase. Another problem is that the Sound Library Manager no longer connects to the Monologue because it apparently requires the Korg driver.
The new Windows MIDI service is not yet activated on my Windows 11 system.
Neither Cubase 11 or 15 work with the windows 11 update. Has Steinberg acknowledged they need a fix. I tried everything and my new windows 11 pc is useless. What the heck? I don’t expect any help from Microsoft. I’ve never had this kind of issue anf I’ve used Cubase since it was created many moons ago.
If you want new-style port names with the m-audio device, grab the MIDI settings tool in the SDK runtime and Tools installer, find the m-audio device and pick “personalize” near the top. Then in the window that comes up, set the naming approach to use new-style names.
Just to clarify. I disconnected my Midisport 4x4, uninstalled the drivers (automatically and manually removed any remaining data), installed KB5077181, everything works, and then reconnected the Midisport 4x4 Anniversary Edition, installed the MS drivers, and everything seems to be working fine. Thanks for your tips.
Hello Pete,
I’m trying to clarify my “concern” regarding the port names a little further.
It basically concerns the port names in connection with Cubase and the MIDI remote.
I use an M-Audio Oxygen Pro and a Korg nanoKey Studio as MIDI remote controllers.
The Oxygen Pro has always used the Windows driver called “Oxygen Pro 61.”
Yesterday, I switched my nanoKey Studio to the Windows driver. It is now called “nanoKey Studio” and had a different name before.
As a result, the MIDI remote script can no longer be loaded. It is possible to adjust the port names within the file, but I am not a programmer and cannot find the entries in the file.
I have now started to set up the nanoKey as a “new” MIDI remote with the Windows drivers and port names. So far, this seems to be working.
My Oxygen Pro 61 is safe because I already use the Windows drivers there.
My questions are:
When the new Windows MIDI service is activated, will the port names change again or will they remain the same?
From your screenshot, I can see that a new page will be added to the MIDI section in Windows 11?
It all looks a bit complicated to me, but as I said, I’m not a programmer.
Thanks in advance for your help.
Did you follow the instructions above covering how to use the MIDI Settings app to change the naming style?
And if that doesn’t match what the driver was providing, you can also provide completely custom names in that same app, and those are what Cubase will see. No programming required.
I have the same problem mentioned here, I have both the silver M-Audio 8x8s and 4x4 blue Midiman midi interfaces. When using them it seems to work first time, but when exiting from Cubase there are active sessions still showing in Windows MIDI and Musician Settings application. If I then try to open up Cubase again, then it hangs. To get around this I have been turning off all midi devices and rebooting, 9 times out of 10 gets rid of the active session in the windows midi app. If the session still exists when rebooting, a further reboot fixes it.
I have several synths using usb midi, also Korg SQ64 and Novation 49SLMK III which are work fine when not using the Maudio / Midiman interfaces, they leave no active sessions after quitting Cubase etc.
To me it looks like it is something to do with the active sessions not being closed when using the M-audio interfaces.
I also get Ableton hanging like Cubase with the midi interfaces.
There’s a pinned post in announcements covering this.
The inMusic (m-audio, Akai, etc.) drivers hang on shut down. They always have, but most folks wouldn’t have noticed because in the old stack apps talked 1:1 with the driver, and they were quitting the app anyway. Disconnecting the device and plugging it into another USB port would reset it in those cases. Now with a central service, it hangs most everything because we have to disconnect and reconnect devices regularly to support multiple apps and multi-client use.
The devices are fine, which is why they didn’t come up as failing in our testing with our in-box drivers. It’s the inMusic driver that’s having issues. We’re working with inMusic folks to find a solution.
In the meantime, for all modern Akai, m-audio, RANE, etc. MIDI devices, we recommend using our in-box driver as those devices are class-compliant and there’s no need for a third-party driver. For the older ones that are not class-compliant, they need to be disconnected for now.
I am not connected to this brand, but I can say it might be worth having a look here: https://miditech.de/en/produkte/usb-midi-interfaces/. The class‑compliant devices are well built, similar to Midiman/MidiSport. After unpacking, I recommend letting the device air out for a few days, because it smells quite strongly of fresh electronics and solder.
Hi - yes, I had a look through a few devices including these ones but according to my actual cable setup I need the 4x4 device look the same as Midisport 4x4 (i.e. all 4/4 ports on the back). But anyway I am sure the Anniversary edition will be OK.
.