A few days ago cubase crashed, then when i exit cubase and startup again its only spinning. I go to task manager and i see cubase is running efter i exit. I have to reboot pc and then cubase starts, except from a popup telling me i have have to choose startup my settings og startup withouts preferences etc, I can also send report to steinberg by clicking a button.
I also see that cubase dont remember the last project in cubase hub. I have to go in windows and start up latest autosave projet from there. It then startup, but if i exit and try to startup, the mouse arrow just spinning, when im in Taskmanager i see cubase tunning and i force shutdown there. Then i startup cubase again and it loads but stops with “initializing all Midi”. So then i have to reboot PC for cubase to load. when its up running its all normal.
I have reinstalled audiodriver “fireface800” i have checked that all drivers are update on display drivers etc.
Im on Windown with i9 and 64gb DDR5 ram. Machine have been rock solid for 3years.
Until now!!! Anyone who can help with check my pc remote. I can pay for this. I need machine to work as normal ASAP
When Cubase crashes it typically creates a crash dump file and places it in the \Documents\Steinberg\CrashDumps folder. Post your dump files here where the file data matches the time of the issue you’re describing.
Myself or someone else from this forum will be happy to analyze this dump file for you which will most likely tell us what the issue is and we can take it from there. Without the dump file we can only speculate.
You where absolutely right. Now all is ok, but I cannot program CC on strings because I used the midisport to connect a controller to the DAW. I guess the Solution to this is to buy a New usb midi
I try to map the fireface midi so I can use the controller trough this. But I never got this to work. I guess it’s lack of knowledge so I guess I have to buy a newer usb unit to use midi controllers
We’re working on figuring out what is wrong with those drivers. I ordered a bunch of those various models used via Reverb, but they won’t be here for a week or so, which because of travel coming up, means I won’t be heads-down debugging them until May. Then it’s a couple months before any fix can make it into the OS.
So they may eventually work if we can find a way to work around the bugs in the m-audio driver. But it won’t be in the short-term
The black & green anniversary edition versions of those are class-compliant and so will work without any vendor driver.
Yes i saw the Anniversary but I think this time i will do a serious attemt to get the mapping with fireface midi and the fader control i have. If I can get this to work I don’t need the midisport2x2, this would be the best. (Less components, less drivers). But still I do not understand why the fireface midi don’t work. Or what I’m doing wrong.
I don’t have one of those, it’s out of production and the last driver update says 2019 and only supports Windows 7 to Windows 10 according to the description. That said, if you have audio working with it, it obviously works.
Did you ever see MIDI ports from it in Windows? I assume you’ve had it longer than the past month.
If you have the Windows MIDI Services SDK and tools installed, can you open a terminal window and send the output from running midiksinfo so I can see if we see any MIDI pins on the device?
It’ll look something like this. Screenshot (if it all fits on one screen) is fine, as is just copying and pasting the text output for the Fireface 800.
Hi Pete - it would be nice to find a solution for those (Midisport) interfaces since I have 2 of them (4x4 and 2x2) and I actually do not wat to find any newer MIDI interface as a substitute….thanx a lot for working on that!
I had exactly same problem, but I am new in Cubase, and lived with that couple of months, as I am not using Cubase much. Removing Cubase from NVidia driver helped me resolve this problem, I wrote in another topic (maybe it help):
I’ve been having problems with Cubase, Native Access, and Spectrasonics for the past two weeks. The programs wouldn’t start or (Cubase) would get stuck at the MIDI or Initialize All MIDI Inputs stage.
The culprit for me was the Windows 11 update KB5077181.
I uninstalled it, and everything is working as before.
I’m working on it, but it will take some time to investigate once I get the devices here.
It’s also entirely possible we can no longer paper over the issues with the third-party drivers. We try hard for backwards compatibility, but can’t make promises.
They don’t work on macs anymore either, but someone who really wanted them to work created their own driver. I’m impressed.
Pete - what about Steinberg MIDEX8 interface, are you able to check it (or give me some instructions I am able to do the checking directly on my side) whether it is OK with new MIDI roll-out in W11 or whether it can cause similar problems like older MIDISPORT versions?
I don’t have a MIDEX 8, and it looks like they require a driver on both Windows and macOS so it is likely not class compliant.
It’s hit and miss with devices tied to old drivers. So far, it seems only the ones from inmusic brands (AKAI, m-audio, etc.) are running into issues. We’re working to get that fixed, but old devices that aren’t class compliant will eventually stop working someday as they require someone to maintain drivers. (The MIDEX ones were last updated in 2011)
You can’t even easily install the MIDEX drivers or download the manual now unless you know how to use an FTP client. Modern browsers generally don’t do FTP anymore.
