I updated to the latest release now it won’t open it’s stuck at initializing midi. What is the fix for this?
It happened before in 15.0.10 and I think I got a popup screen when I tried to open it again after a task manager shutdown from Cubase to send the files to tech support which I did and I believe I clicked on deactivate all 3rd party plug ins and it worked Even tho that was a pain and I had to reload or rescan all of my plug-ins even Groove agent etc. now that won’t even work!
Barring having to go down the windows rabbit hole and roll back updates and restore to an earlier time, isn’t there a simple fix for this? Seemed to work last time but not now.
If you’re on Windows 11, and Cubase is hanging at “Initialising MIDI …”, try uninstalling any vendor-specific MIDI drivers (not applications) for USB MIDI interfaces and controllers. They should work natively with the new Windows MIDI Services. If this is the issue, reverting to earlier Cubase versions on Windows 11 will not fix it.
Link to the information about Windows 11 MIDI Services:
If you have any inMusic devices (AKAI, m-audio, RANE, Numark, Denon, etc.) there’s a known issue with their driver which will hang the service.
MrSoundman is correct. If the device is USB MIDI 1.0 class-compliant, you’ll be better off uninstalling the vendor driver and using our in-box drivers.
If it’s an older device (> 25 years or so), or a combined audio/midi device, you cannot do that, so you will need the fix we have on the Discord server. Windows MIDI / Audio and read the pinned post in #start-here
Depends on who you ask. Most folks say that macs “just work”, but then if you frequent the support forums for macs like I sometimes do, you see they have issues as well.
For MIDI in Windows, it’s a unique time because we just completely rewrote MIDI in Windows, and have found issues and have been rolling out the fixes for them, including workarounds for third-party driver bugs.
But please keep in mind that simply installing the update is not enough to get hte fix. Enablement comes any time in the 30 days following the release.
I’m not sure what fixed it it just stopped hanging and opened up. I did not download any workaround or windows fixes. After I tried all the hard closes and total shutdown of the computer I fired it up again and then did restart (not shutdown) opened Cubase and walked away. To my surprise it opened up on its own. I could not tell you how long it took to finally open up but I didn’t come back to check for over an hour.
I’m having pretty good luck with the latest but have had a couple of freezes of the MIDI.
I’m actually excited about these changes! I’ve been hoping for more attention to MIDI in Windows and was glad for the announcement!
Pete, I’m hoping your work with this and proximity to MS has helped identify various OS and utilities that cause “stutters” in Cubase that I’ve spent a lot of time trying to deal with. Regardless, the improvements thus far are welcome!
Almost all stutters and DPC issues are caused by third-party drivers, with GPU being a big one. Otherwise, most services, utilities, apps, “bloat”, etc. have no actual impact on audio creation workloads. We’re working with OEMs and our own internal OEM (Surface) to improve that and get DPC latency on everyone’s minds.
But it’s really going to depend on what you purchase. For example, if you buy a PC designed for gamers, it’s going to prioritize FPS and Network above all else.
Appreciate all this but it’s getting all “techy” and not something people want to mess with while trying to put down an idea. But thanks for working behind the curtain?
Without disputing any of this, it’s an ongoing frustration for some of us that these issues generally lead to everyone pointing elsewhere. We do not see the efforts behind the scenes for the cooperation, or lack thereof, between vendors. Frequently, what “we” see is, “It’s not our problem!”
To whatever extent your efforts bring these issues to the forefront with vendors and facilitate better cooperation and acceptance/regression testing, it will be welcome.
As recent as yesterday, a suggestion to at least document known problematic hardware or VSTs was characterized as unreasonable because it could cause issues between vendors. Obviously, this is problematic to end users, even those of us with considerable experience.
Anyway, my intent was to express appreciation for addressing some of the MIDI issues and native support for things that previously required third-party solutions. To whatever extent you identify problems and work toward solutions as part of your work, it will be appreciated.
Appreciate all the behind the curtain work everyone does for sure. Consumers however as in most things they buy from Windows, to Cubase, all the way to purchasing autos, health care, tv’s you name it have to somehow decipher all of these vendors issues and make things hopefully work with the least amount of aggravation. Thanks for the feedback.
Was that recently? I’m not aware of any current issues which would cause that.
The issues I’m currently aware of that can hang Cubase when it is initializing MIDI are ones from those inexpensive Arduino (or similar) controllers which ship a broken MIDI implementation. Some of them thoughtfully contain a piece of paper saying not to enable MIDI Out if you use them from a DAW.
We have a workaround for that coming in November, but it does leak some resources as a result. So we’re trading memory and thread resources for service responsiveness.
This is one of those types of issues that is 100% the fault of a third-party developer (they ship the tutorial code), even though folks don’t necessarily want to hear that, and they expect Windows to just fix it.
