Subpantelis wrote:As I said before, it hangs on exit even with no project loaded. If no project is loaded, then no plugins are loaded, right? So in my case, it's pointless to look for plugins as a culprit. It's probably rather a driver, or some USB thingy.
Who can say for sure? Not me... I don't know the inner workings of Cubase and plug-ins. I am just an unfrozen caveman lawyer.
I know Cubase scans them, and "communicates" with them on start up. Maybe it tries to communicate again on shutdown. I would say it is worth a try to start with a clean slate.
Good one, Jaslan!
Surely one must concede to the possibility that a component could get stuck even if the Cubase project closed, e.g. if not programmed according to specs, or try imagining something unexpected happening.
A light bulb flickering is not necessarily caused by the bulb, nor is a disturbance necessarily caused by the electric company. A click heard on a speaker while playing audio isn't necessarily caused by the audio source, nor the speakers. Network loss with a *smart* phone, or other device is not necessarily a fault of the device, nor the phone company. E.g. an air conditioner can cause any one of these things to happen.
However unlikely the consistency of these particular scenarios are over time, they present a visual for how things happen in more complex systems, and how one arbitrarily node within a system cannot bear claim without some decent evidence. A symptom is not evidence of cause. "Waking up one morning with an extra fat lip, doesn't mean one has been attributed with elephantiasis, even if's the only explanation one can think of."
A computer has many different parts and if you happen to have the one thing that just doesn't work with your system, you will experience problems. Even if two computers have the same components (which in itself can easily be just in appearance), software that was installed in a different (or sometimes even in the same) order, could mean that the computers are not operating identically.
You need to find out what it is that is causing *your* problem, because as a contrast, I and others are not experience this particular issue that is described. So this difference cannot just arbitrarily be attributed to Cubase, which is why Steinberg is welcoming you to contact their support team, which will help you find the cause. Doing so, could minimize the issue over time, since they could learn of things that could potentially be worked around. Does this mean it will be eliminated? Probably not, why? Well, I think I already gave my opinion on that.
Also, the project data doesn't really have anything to do with the instances of plugins, other than communication of various data, i.e. note on/off, patch data, etc.. E.g. play this note, stop that note, give me your properties, set these properties that X, and so on.
Cubase *is* a complex application (like any the DAWs out there) for sure, but it isn't the only software you are using. All kinds of drivers, plugins are being utilized, not to mention the ones that has nothing to do with Cubase per se. This does not preclude them from potentially causing problems. Email programs, browsers, instant messengers, social media apps... well, the list is long.