On a PC, running the latest Cubase, and Windows 10
95% of the time when I “close” Cubase with an open-active project, once the project has closed, and you would expect Cubase to then quit, it hangs, and I have to end the task
75% of the time, if I have an active project, load a 2nd project and choose tp activate, the project will load, and then cubase will hang as soon as I try to go anything (like play, or change the tempo, or open a midi part ect)
Many times, if I first “close” a project, it will close fine, I then go to the menu to chose “file/quit” as soon as file -highlights-…Cubase will hang.
Not sure if looking at the crash logs will help, is it even a “crash” if the process hangs and stops responding?
Feels like Cuabse has always been a bit like this, but seems much more consistant these days, I get like one clean quit maybe in a day if I am lucky.
Is it possible to look at the crashlogs in a meaningful way these days? I know on older versions, you could open them up in a text viewer and figure out which 3rd party plugin was cusing the crash. But like I say, is a hang, the same as a crash? Would the logs even be meaningful?
Anyways…I’ve waffled on enough. any pointers?