Cubase 15.0.1
Was having trouble on boot ‘Initializing: All MIDI inputs’.
Had to restart my computer.
That solved that,
but now Cubase is hanging up on a project load I’ve been loading repeatedly for the past 2 weeks without problem.
edit
It’s now stuck on Initializing: All MIDI Inputs again after force quitting Cubase on the failed project load. And it’s doing it with Disable Preferences boot up as well.
edit
Just tested Cubase 14.0.41, also stuck on Initializing: All MIDI Inputs.
Hi,
Please, read this article.
I know it’s what folks are used to doing, but I wish you would not uninstall the updates, or at least wouldn’t recommend that others do it.
I keep running across customers with broken MIDI systems because they uninstalled updates which were just the fixes to the January release. It results in a partial MIDI system and to recover you need to go into Windows and use the Windows Update recovery option.
We have workarounds / solutions for the known issues on the Discord server.
Windows MIDI / Audio (see the post in #start-here that the link lands you on)
Pete
Microsoft
Being in the middle of a gig, I needed the fastest resolution.
But oddly, everything has been working fine for me up till this morning when it did those latest updates… So did the fixes break something for me?
I don’t have Discord…
edit
The uninstalled updates have reappeared in Windows update as ready to install…
The “Initializing MIDI Inputs” hang is usually the result of an inMusic driver (AKAI, RANE, m-audio, etc.). The driver has a bug. That bug impacts MIDI much worse with the new stack because it doesn’t just cause a single app to hang on close, it causes the entire MIDI Service to hang when we try to close the open MIDI input.
I use Discord because it’s easy to keep the instructions there, point people to them, and also help if something doesn’t work. (Otherwise, I have to chase folks all over the internet, reposting the same info.) If you are not interested in going on to Discord to get it, the fix will start rolling out in Windows at the end of this month, so there’s not much longer to wait. It takes up to 30 days for the feature (a fix in this case) to be enabled on all PCs.
Pete
Microsoft
I don’t know if this is connected - since yesterday I got horrible dropouts and Asio peaks on projects that I worked few days ago without any problem (no midi or VST instruments - just audio tracks and plugins). The onnly thing that changed in last 2 days - are some Win 11 updates. Anyone experienced something similar?
Okay thanks pete,
The only MIDI Drivers I have up and running atm are for Korg padKontrol, Novation 25SL MKII, iConnectivity MIO XL, Intellijel uMIDI. The Korg and Novation are old devices.
So I suppose I will leave the uninstalled updates as uninstalled so I can keep working, or?
For the KORG, I recommend uninstalling their driver if you are using it. It’s not needed, and does cause problems under the new stack. (What you listed are MIDI devices, but some may be using our in-box class drivers, and some may be using third-party drivers).
For the mio XL, if you are using rtp on it, you will need the fix that is on Discord now and goes into Windows starting at the end of this month. Otherwise, the rtp ports may not show up.
Pete
Microsoft
So uninstalling the Korg driver should solve my issues?
not using RTP yet
Seems like the USB driver for my Novation 25SL MKII goes dormant as well, turning the unit on off doesn’t fix. Have to reboot the PC.
Those are class-compliant, IIRC, and don’t need drivers. But I see they offer one for download.
This is the first I’m hearing of this issue. Maybe try the same fix we offered for the inMusic drivers (although I’d be surprised if this is the same thing).
Windows MIDI / Audio and read the pinned post in #start-here . It will point you to the right place to get the preview and the instructions for how to install it.
Pete
Microsoft
