Hello! I have a high-end PC, but I don’t understand why I have to wait 8-10 seconds until Cubase finishes closing. Usually, I just kill the Cubase 15 process and that’s all. For example, my other DAW, Ableton Live, closes in 1-2 seconds.
1 Like
There seems to be 2 running services Steinberg Media Bay Server and Steinberg Licensing Engine that continue to run after closing the Hub. On my PC it is more like 20+ secs until these processes end. If you shutdown your PC before they end, Cubase will think it crashed and present you with the ‘Do you want to run with existing preferences’ etc. screen the next time Cubase starts. I understand Steinberg likely uses these services in other products but why cannot each one immediately sense when there is no longer a need for them and end them.
2 Likes
I wait, just in case killing the process might screw with the file.
I’m usually in a hurry to open Cubase, but why the rush to close it?
1 Like
Wait… to do What?
3 Likes
Very bad idea. Many things are written on close. You’ll lose settings and have other issues if you don’t close properly.
This is your call. But you did ask.
7 Likes
I take it for Cubase to unload all the VSTis, plugins, etc.
Wow you are impatient. That is not that long and depends on what’s loaded. Really not a good idea to kill the process. Don’t you find Cubase starts the next time and you have to choose if you start normally. You will end up with corrupted projects.
2 Likes
Cubase writes all changed application settings to configuration files (like Defaults.xml, UserPreferences.xml) when it is closed. If the process is canceled, Cubase cannot do this and the setting changes made during the session are lost.
In addition, Cubase closes the SteinbergMediaBayServer.exe and SteinbergLicenseEngine.exe processes properly if no longer required by other (Steinberg) apps; if the process is canceled, they may continue to run unnecessarily.
The entire process takes about 20 seconds, is invisible, consumes hardly any computing power, and doesn’t block the computer for other tasks. Therefore, it’s strongly advised against aborting the process to quit Cubase.
2 Likes
Indeed I always find myself closing the project and then wait until its safe to quit Cubase because I will get the crash popup next time I open it. Really annoying.
1 Like
Yes, I understand that. What I mean is, Why can’t you do something else for 10 seconds? Check your emails? Check this forum? Have a scra, I mean stretch?
2 Likes
My other DAW, VEGAS, can take up to a minute. (OK, I know, but it started out as a DAW.)
Digital stress!
Never heard a plummer complaning putting down his tools and closing the toolbox; had to wait a minute or two? 
Wow 8-10 seconds. I just can’t imagine the hardship you are dealing with having to waste all that precious time, just because Cubase needs a second to wrap up the MediaBay and clean up its resources..
Thoughts and prayers!
2 Likes
Do you understand how a computer works?
Don’t do that. Eventually you’ll end-up corrupting your project(s), your preferences, or both. You could “save time” by unplugging your PC instead of shutting it down, but most people understand why that’s a bad idea. Killing Cubase is the same thing–unwise, and totally not worth the risk.
Yes–and stopping a golf cart takes less time than stopping a train.
2 Likes
Its a legitimate complaint. Some folks are fried at the end of a long day and the 1 to 2 minutes (for me with larger projects) is annoying and could be remedied in the code.
1 Like
You must be on an older version of Vegas? V23 closes instantly here. In fact it has for the last 4 or 5 versions.
I love Vegas btw. Glad to see another user.
The topic is posed as a broad community question to gather input from seemingly more than one person.
Pete
Microsoft
1 Like
Ok. No worries. 
1 Like
I wouldn’t complain if it shut-down faster–but I hope they prioritize BUG-fixing over optimizing the shutdown process. They start taking a bunch of shortcuts with that, and we’ll be on here crying about corrupted projects that can’t be opened in the next session.