After installing Cubase 15.0.2, the application won’t finish the startup sequence, it hangs during initialization of MIDI.
I have “repaired” the MIDI driver.
I have reinstalled the update (Cubase 15.0.20).
The issue persists.
Nothing else in my hardware / software configuration has changed other than the release of Cubase 15.0.20. I keep the machine clean - no freeware, no trials, etc.
I keep the OS current.
My configuration is:
Hardware: Lenovo Desktop running most current version of Windows - patched.
Hardware: MIDIMAN (M-Audio) MIDI SPORT 4x4
Are you using the new Windows MIDI Service (‘new MIDI stack’)? If so, the drivers for Akai, M-Audio and others are currently broken and are being fixed. In the meantime, there is a workaround available. Check out the Discord server here: Windows MIDI / Audio or Github here: GitHub - microsoft/MIDI: Windows MIDI Services · GitHub
it’s most likely Windows 11, and not Cubase that’s causing your issue. If you have any drivers installed for the MIDI SPORT 4x4, try uninstalling them.
See this announcement and the links therein for more detail:
This is a problem with the inMusic drivers. They have always hung on close in the past, but the impact was minimal (usually resulting in a zombied app in task manager, or just requiring you to unplug and replug the device). With the new service, they hang the entire MIDI service.
InMusic is working on a fix for some of their drivers. In addition, we have a preview workaround for the driver bug available on the Discord server Windows MIDI / Audio . Please read the instructions in the #start-here channel. This same code goes into Windows starting at the end of this month, but it’s available on Discord to unblock customers today.
Note that without further driver changes, these inMusic drivers will still crash the service/apps if you unplug or power down one of their devices using their drivers while the device is in use. We have no workarounds for that.
Newer midisport devices (black and green Anniversary Edition, and the blue 1x1 Uno) do not need inMusic drivers because they are class-compliant USB MIDI 1.0. Similarly, the newer Akai controllers also do not need their drivers. In both cases, you can uninstall the inMusic driver and use our in-box MIDI Class driver, just like you would on any other operating system.
Thanks for that. Yes, I’ve uninstalled the drivers for my old (blue) MIDI SPORT 4X4 now Cubase 15.0.20 will complete the startup. Would the path of least resistance be getting a newer MIDI interface - a model that doesn’t require drivers and is just “recognized” by Windows & Cubase? When I open a project now, I get a popup for the unmapped MIDI ports.
Possibly. I’m faced with the same problem – I have been hacking the Midex under Windows 10 for years, but that’s been finally killed by Windows 11 now. The key question is whether or not a (MIDI interface) device is “class-compliant”, if yes, then no OS-specific drivers are required.
I’m currently looking at ESI, for me the M4U eX would replace the Midex 8, it has only 8 physical DIN-5 connections but each one can be used as either an input or an output, which is really flexible,
You can still use the inMusic drivers with the service update, as long as you don’t disconnect them when in use. See my post here for info on where to get the preview if you need it within this month.
So entirely up to you.
Test results from me and from customers on Discord.
