Cubase wont close properly after exiting.

[bibz1st]

Hi all,
a friend uses Cubase 11.5 on windows 11 and whenever he tries to exit the program after closing a project it refuses to disappear and task manager says it is not responding.
Uses Omnisphere mostly if thats any help
I'm unsure of his pc specs but it worked ok with version 11, no issues doing anything else.
Any ideas ?

[tehlord]

Cubase has been like this since 1848

[trtzbass]

Yeah that’s the ‘ol Coobs

[middle_color]

Hi all,
a friend uses Cubase 11.5 on windows 11 and whenever he tries to exit the program after closing a project it refuses to disappear and task manager says it is not responding.
Uses Omnisphere mostly if thats any help
I'm unsure of his pc specs but it worked ok with version 11, no issues doing anything else.
Any ideas ?

Do you use Menu: File -> Quit? Or you just closing a window with the "X" icon?
When not using "Quit" command it will close poject, but main program still running.
If you do use "Quit" command and still have Cubase running for more than a minute, then it probably stuck Which is not uncommon for some users.

[bibz1st]

Usually the 'X'to first close the project then 'X' to close Cubase. As I said, previous version didnt have this behaviour.

[Origin8tor]

I first posted about this in this very forum about this in 2018, and I know it goes back much further. I was "doing a task manager intervention" everytime I closed Cubase until recently, since they introduced software protection even that doesnt work if I want to restart Cubase without restarting the computer, the Steinberg Licensing process gets glued up and Windows installer is stuck trying to install a media bay update! I must have submitted my crash logs to Steinberg more than 100 times over the last few years, nothing, their support doesnt even acknowledge it as a bug, citing the ol' its [you, your PC, a plugin (but we're not sure which one), an extension (again, not sure which), a MIDI device, Windows Updates, Google Drive or Dropbox, or anything else that isnt our software or responsibility)], It really is a joke.

For me, Cubase is a great piece of software and, when its not not starting up, my favourite DAW, but years of the same 'ol head bashing has taken it toll, its a real shame.

Im no expert, but I reckon if Steinberg can code all the amazing things that Cubase can do they should be able to shut the software down cleanly, maybe its the will that is missing?

[bibz1st]

It shouldn't be happening but its not really a problem to me as I only use cubase when at friends place and I use different daw at home. Maybe it wont happen in next version which he'll probably get so just have to see when the time comes.

[rasmusklump]

For the most time it's an issue with a specific plugin.
Think of a plugin you have in every project. In my case it was the old Limiter No 6, that I had on the master channel in each of my projects.
After uninstalling this the problem was gone.

[D-Fusion]

It shouldn't be happening but its not really a problem to me as I only use cubase when at friends place and I use different daw at home. Maybe it wont happen in next version which he'll probably get so just have to see when the time comes.

My experience is that Cubase is a horrible Daw when vst's are used compared to the rest of the competition and works best for hw instruments.

It has a crappy Audio engine and it likes to slap the cpu usage around if it doesn't like the cpu you use.

It works great with my Amd 5700x but not so much with my intel 12th and 13th gen (even with e-cores disabled).

[kritikon]

I think Cubase has always had shutdown problems for me, going back decades. Can't remember having any version ever that didn't need more than one go shutting it down, whether on AMD or Intel. I thought it might have been dongle issues, but lo and behold, dongleless made no difference whatsoever. It's a very minor issue though and never really bothered me - just one of those things you get used to.

[bibz1st]

Its like its not letting go of some resource or something, maybe cant unload vsts, dont know.

[jancivil]

Right. Check Cubase's preferences, Plugins tab: uncheck 'Keep plugins in memory until application quits' and see if that changes the behavior.

[4damind]

One of the problems Steinberg never fixed. There are also the well-known "crash on exit" problems, i.e. the next time you start Cubase you get an error message that Cubase has crashed. Yes, it probably has something to do with plug-ins not unloading properly. Steinberg doesn't have a solution for this and the problem has been around for quite a long time.

[BBFG#]

Right. Check Cubase's preferences, Plugins tab: uncheck 'Keep plugins in memory until application quits' and see if that changes the behavior.

Had no such option in Cubase Elements 11.4x...
Have had the issue others are talking about, but only by mouse clicking the x exit.
Immediate quit with Cntrl-Q everytime though. So they differentiate between exit and quit.

[kritikon]

I'll have to try ctrlQ. I've had the crashing thing on startup - worse with C12 than any other version I had. After one time, I had to reinstall Cubase as it would refuse to fully load up again and again (original C12 version). Hasn't done it for a while now and seems to behave, so I guess updates have fixed it. I never figured out why it crashed and locked, and hadn't deleted any plugins, so it's doubtful it was a plugin's fault. I tried deleting preferences & default reset according to Steinberg instructions, which obvs did f**k all to fix it.

I really like Cubase, wouldn't have stuck with it for decades if it didn't work for me, but sometimes it gets exasperating that they can do all kinds of wizzbang magic with midi & audio but can't even code the on/off button properly.