So Cubase 15.0.10 and Windows pro 11 (version 10.0.26200 build 26200) Either one of them has changed the working setup to something horrible. What I notice: I’m missing the “quit cubase button” on the hub, while nothing no Cubase windows is visible or open. The menu “file -quit” menu on the hub entry is there though. That kills the hub, but not the Cubase process. Subsequent start ups of Cubase do nothing at all:
It feels like Windows/Cubase have trouble initializing and releasing Midi ports now.
Only thing I can do is restart machine, and have one possibility to start Cubase, and hope that one won’t freeze at Initializing ‘All Midi Inputs’. Anyways Will keep spanning Steinberg with my logs. This is not funny at all.
Hey Martin, thanks for your reply. You got it right. Well it looks like it is rather a Windows update / incompatible midi device driver thing. I’m able to run flawlessly without System Core Isolation protection. (which is not recommended these days) So my setup that worked fine for so many years doesn’t work now. it is getting old like I am. Not that compatible anymore.
Note that in this situation when I kill the tasks and start Cubase again, you guys first get sent a log file. Secondly Cubase will hang on ‘Initializing All Midi Inputs’ probably that’s all.
Update: Nope, All my device drivers are class compatible and trusted. Running Windows with core isolation off does not have an impact. Cubase (or Windows) does not release the midi (input?) ports when shutting down Cubase. Need to kill Cubase process, and then after starting a new instance of Cubase it hangs on ‘Initializing All Midi Inputs’ So effectively requiring a restart of the computer.
This will tell you the status of Midi services on your machine. The rollout from Microsoft is ongoing right now and some issues have cropped up along the way.
I’ve had one occurence that sounds like this situation - and appears it was related to something funky going on with Loop midi and the WIndows MIDI 2.0 update. I killed cubase in Task manager and rebooted - everything was clean second time around and has been every time except this one occurence.
Unfortunately I picked up the MIDI 2.0 update as part of another fix in that particular patch that I needed (unrelated to MIDI). Aside having to restart the services on boot after loop midi has started it has been working just fine - just this one peculiar moment when midi went mad and cubase hung (other apps just stopped working with midi).
I’ve seen one instance where the rtpMIDI Service was preventing proper disconnection of other WinMM ports, causing an app to just hang. I don’t have enough data yet, but we’re looking into it.
I’ve just reinstalled windows 11 clean as i swapped out my x670 MOBO for an x870.
I’ve done a clean install and sepnt all week reinstalling all my software.
Today I fired up Cubase to start work and I’ve been struggling with freezes all day and they’re all to do with ‘midi’
Cubase stalls on initialising midi and once that’s happened depite killing Cubase in task manager it will carry on freezing. I have to reboot to get it to work. I’ve tried using RTmidi … should I need to do this? I remember from a few years ago I had issues and using the MMCSS fix with win RT solved the issue. However both Nuendo and Cubase are really unstable ATM with midi being the issue.
I have connected…
nektar GXP keyboard USB
An M audio Oxygen keyboard USB
My roldand RD770 conected via the UFX midi port
Crumar drawbard which appear as ‘Arduino’
A small 2 fader cc controler also seen as ‘Arduino’
when I checked i didn’t havew the new midi 2 services.
This situation is pretty awful as my Mac M3 ultra worked completely reliably and issue free but I fond it wasn’y as powerful as I’d hoped and thought I might as well go back to my 9950x machine.
Hi Pete, thank your reply. I’m NOT using rtpMidi. The legacy interface 5 pin din to usb is causing issues now I think (though compatible drivers) . I ordered new hardware just in case. Device ran perfectly for years so even not bothering switching to WinRT. Now when I actually do switch to WinRT mode I have some good and some bad news. Good news is program does not freeze on ‘initializing All Midi Inputs’ it just takes a long time. Also good news Cubase actually closes, but that also takes a long time being shutdown as ‘background service’ as there no UI left. Bad news is that in WinRT mode I see midi meters moving within Cubase but no midi is actually recorded. (will test again, because strange). Anyways I think some work still to do.
yes, there’s something needs adressing here with Windows and Cubase.
For the record, Reaper runs faultlessley with all midi devices.
There is no options in which type of midi to use in reaper, it’s just like on Mac os, you just have ‘Midi devices’
So the issue here is Cubase and Windows midi…. theres definitelty something needs sorting out here.
I have a fresh , vanilla install of Windows 11 and Cubase 15 on a high end machine and it’s NOT working.
I tested this machne against my M3 ultra and it performed better….. at the time though there were no midi devices conected to the machine and it ran great. This lead me to buy a new x870 MOBO and do a fresh vanilla install of everything so I could transition form the M3 to the 9950x. As soon as I added midi hardware Cubase became a problem.
I just ran the MS Midi checker tool and it appears that the Midi 2.0 services are installed on my machine. This is an i7 14700K rig with an Asus Z790 mobo. Windows 11 latest updates and Cubase Pro 15.0.10.
These are the Midi devices connected:
Yamaha DTX700 kit
Arturia Beatstep Pro
Novation Launch Control
M-Audio Hammer 88 Pro
Faderport Classic
All devices are working as expected, Cubase runs as normal.
I’m not using Midi loopback or multi-client.
If I hadn’t run the checker I would have had no idea that anything had changed.
@Psychlist1972 If the checker tool says Midi 2.0 is installed, is it actually active yet, or does that follow later?
I updated windows again last night before i left the studio and this morning when I ran the windowsd midi services app it did indeed show I have the new Midi 2 enabled.
I have 2 controlers that are based on Arduino , a draw bar set and a 2 fader midi CC controler. I unpluged these and used standard midi cables into a midisport 2x2.
I launched Cubase and checked the midi devices and unchecked the MIDI RT. I also noticed that I now no longer had loads of Euphonics midi ports which I had before, so not sure why but they’ve all gone but it certainly tidys up the midi ports.
Anyway, with the new windows MIDI and the midi sport I’ve had zero issues today and Cubase is running like a dream…..
Nice!