I’m a bit of a workaholic so I work til I drop. On my Win 10 PC I have Cubase 11, two other DAWs, Microsoft Office suite, Adobe Creative Cloud suit, and various software development tools.
I’ll typically work until 11 or midnight, leave my applications open, and go to bed then come in the next morning and resume what I was doing. I never have this trouble with other apps such as Premiere Pro, Photoshop or Microsoft Word, but in the morning I often find that Cubase is Dead. It happened again this morning. I’ve attached a screenshot.
I find this happens about a third of the time I leave it unattended overnight. What is it about Cubase that makes it sensitive to being left unattended overnight? Crashing while it’s sitting there doing nothing is very unprofessional and interferes with producers’ productivity.
If your system has USB devices that sleep after a certain amount of minutes or other peripherals that can cause an issue
Nothing else on my PC except Cubase does this. I have lots of apps that I leave running on my PC overnight that use USB devices and are not frozen when I come in in the morning. The only USB device that Cubase depends on is the audio system (A Steinberg UR22MkII with the Steinberg USB driver) and everything on the PC uses that same audio interface, but aren’t frozen in the morning. I can’t emphasize more clearly: this problem is unique to Cubase - nothing else on my computer (mis)behaves this way.
It’s getting to the point where I have to remember to save my projects and shut down Cubase when I go to bed at night or step away from the computer to do other tasks., which I don’t have to do with any other application. Also, sometimes I wake up in the wee hours of the morning or sometimes some music pops into my head while I’m doing something else and I want to run over to the computer and start putting in the notes while that feeling is fresh. I can do that with ALL my other creativity apps because I don’t have to shut them down all the time.
Even if I’m up really late I would always save and shut down. It’s just the right thing to do for numerous reasons. By the way not all other programs rely on usb devices remaining on as Cubase does. Also what about wasting energy!
cubase has always been buggy, stuttering, crashing, freezing…
over the years i been using since cubase 7…
it kinda ruins it because its the best daw (my opinion) i never get issues in other daws like reason, fl studio or studio one pro. the developers take notes you have much to improve in stability of the daw
I’m not aware of any USB devices on my PC go to sleep. And none of my other software has such a dependency; so why does Cubase?
Cubase does auto backup.
Also what about wasting energy!
At night my PC automatically runs malware scans, does backups, or I do long, computationally-intensive graphics-rendering operations. This is a 24/7 operation. My entire studio is on a big UPS that can keep the whole place running at full capacity for an hour which is plenty of time to get my generator running if there’s a power failure. I’m sure there’s a glacier in the arctic my with my name on it melting away.
Let’s get back on topic: : when it freezes (hangs) but doesn’t crash and produce a debug file, what are my options for seeing why it’s hung?
Yes, this is exactly my point. It’s a great product when it works. But it doesn’t work reliably and for someone on a production schedule or who has a backlog of work stability and reliability are more important than fancy features.
So getting back to the question: when it freezes (hangs) but doesn’t crash and produce a debug file, what are my options for seeing why it’s hung?
Is this something that you’ve had happen for ages, or it just started more recently?
I.E. After something like updating from Sonic SE 3.4 or 3.5 to Sonic 7? After installing or upgrading to HALion 7?
Have you more recently updated any of the sounds for HALion/Groove Agent to use the newer dongle-free Steinberg Licensing system (Sonic 3.5.10 and later can work dongle free with a qualifying host such as Cubase/Nuendo 12, or Dorico 4 provided one also takes the latest HSSE library updated in Stienberg Download Assistant)?
It’s a shot in the dark, but some of us ran into some glitches (Steinberg hosts that ‘hang/freeze’, but don’t ‘crash’ or produce crash-dumps) since upgrading to Dorico 4/Cubase 12, and more recently HALion/Sonic 7 that seem to have something to do with the newer mediabay server.
Over in the Dorico forum it was suggested to do this for the time being and it seems to solve a lot of problems for me.
Since starting that manually and leaving it running I’ve had fewer issues. The command line is: start "" "%programfiles%\Steinberg\MediaBay\SteinbergMediaBayServer.exe" "--usermode" "--standalone" "--keeprunning"
I’m not sure this is relevant at all for Cubase 11, but if you’ve taken Sonic/HALion 7 or related updates/upgrades lately it’s worth a shot.
It’s been happening since I got the Cubase - about two years. But it’s infrequent maybe once every month or two.
Sometimes I get outright crashes - but that usually happens when I’m actually using it - these freezes almost exclusively happen when it’s been left up, but not used for along time, but not necessarily overnight. When I’m working on a film soundtrack I spend a few hours in Cubase and then switch to spend a few hours in Premiere Pro, going back and forth -and sometimes when I come back to Cubase it’s frozen even though the PC has been in active use.
I had this same problem. I reinstalled my Windows OS and Cubase and it has not happened since.
That seems like a rather extreme approach. And I’m having no problems with any other apps; of which I have many large complex ones with all kinds of hardware and driver dependencies, so it’s clearly a Cubase problem. This is a Cubase forum so I’m hoping someone could tell me what causes these freezes or how to diagnose them when they happen.
You also said you reinstalled Cubase. Anyway, what was “everything” else? It obviously couldn’t have been “everything” because it didn’t identify or fix the problem. It was only everything you were aware of or could think of, and that’s the same problem I have: Since posting this I’ve received various comments and advice but none of it was specific to diagnosing or debugging a frozen Cubase. Crashes at least give us a crash dump. How do we diagnose a freeze?
Reinstalling (either the OS with all your apps and settings, or Cubase, with all the VSTs and other plug-ins and add-ons) is like using a Patriot missile to kill a mosquito. It may be a really annoying mosquito but it’s still way overkill.
I have been using Cubase since the late 90s. As an every-day user, pop composer…rarely over 250 audio/instrument/group/efx tracks, and heavy VSTI use, even without UAD, the crashes or what you might call freezing/unresponsive happens quite rarely. Sometimes it makes a difference if you buy off the store shelf as opposed to having an audio PC builder configure and built your PC. At the very least, look at what they are using for parts and configuration such as PC Audio Labs, then compare to what you have or want to buy.
With that said, and this applies to anyone, it sometimes can help of you list your computer specs with your forum profile. Especially your graphics card and audio interface. And then if possible, attach the crash reports here.
Well, it doesn’t die on my computer.
Cubase is indeed quite ‘configuration’ sensitive but that’s where you might find the solution:
It crashes on
USB devices going to sleep
MIDI connections unstable
Windows suspending things
Outboard gear being turned off
So how do I keep my PC healthy? (no guarantee)
Clean Windows (11) install twice a year (I abandoned Win 10 long time ago)
I check the device Manager (software devices) and delete (= uninstall) systematically those ‘ghost devices’ )
I read this on the Steinberg site:
When I had a consistent crashing Cubase I did contact support and they had a solution (was NVIDIA driver related BTW)
As I said, this is not a crashing problem; it’s a freezing/hanging problem. It’s not a crash. Cubase remains on the screen but accpts no input and does not display refresh and produces no crash dump, even if forcefully stopped.
If Cubase is indeed uniquely sensitive to the configuration of the PC - more so than other DAWs, professional editing tools like Premiere Pro and Photoshop, or software development and debugging tools like Visual Studio and Android Studio - all of which I have on my PC and none of which have stability problems then that is a problem with Cubase.
It’s perfectly possible to write software that runs on Windows; interfaces to a wide variety of hardware devices and their drivers, and provides safe sandboxes for third-party plugins to run in and everybody but Steinberg seems to know how to do it. It’s nice to know that there are people here whose time has so little value to them that they think nothing of regularly reinstalling their OS (and presumably their apps, settings, etc).
This thread has been going on for days and I still have no advice on how to diagnose a Cubase freeze/hang.