Hello everyone,
I’m reaching out because I’ve been using Cubase 15 for a few days now. I really like the idea of the new Hub, but every time it opens it seems to completely re-sort the list of recent projects. It recalculates everything, and the process is very slow — the Hub becomes laggy and I even get the spinning wheel for a few seconds.
The concept is great, but in practice it feels a bit frustrating. Did I misconfigure something, or has anyone else noticed this behavior? Is there any workaround besides waiting for an update?
On my side, the Hub doesn’t take long to open, but as soon as it does, I can see it start re-sorting all the recent projects — even things it already sorted the last time. And while it’s doing that, everything becomes really slow and unresponsive. It feels like it’s struggling.
So it’s obviously looking for an internet connection when it closes. So for us who choose not to have a permanent connection to the internet from our music computers need a setting to allow for this. Please!
Hmm, not nice. And with internet connectivity, it’s immediate? (I am always online, so I never noticed.). If so, I’d consider that a bug, or a missing setting (but as there is already the “show web content” setting, that should be enough. What else should the hub want from SB servers?)
What I’m experiencing has nothing to do with the internet connection. The issue happens exactly when the Hub opens: it starts scanning all the projects and reorganizing them in ascending or descending order. That process is what slows everything down and even triggers the spinning wheel sometimes. Whether I’m connected to the internet or not doesn’t change anything — the slowdown clearly comes from the Hub sorting all the projects when it launches.
I had the same problem and investigated. The cause is “Steinberg Runtime,” a new background program that’s quietly installed with Cubase 15. It runs constantly in the background and continuously transmits a considerable amount of data to the internet, especially when the hub opens, but also after Cubase closes. This noticeably slows things down. You can easily observe this with a network monitor. If you disable this program, Cubase still works fine (for how much longer, after I report this?), the network activity disappears, and the hub responds as quickly as in previous Cubase versions. Interesting, isn’t it?
No one knows what’s being transmitted. Remarkably, during installation, I had no option to allow or decline data transmissions, unlike with other software (“we only collect your data to improve your experience”).
Thanks a lot for the info. Are you on Windows or macOS?
I checked my Activity Monitor and I couldn’t find anything called Steinberg Runtime.
I’m attaching a screenshot of my Activity Monitor so you can see what I mean.
I’m on Win10. As the Steinberg Runtime module is a sub task, it doesn’t appear as a main task in task manager. I provide is a screenshot of a deeper system info, that shows all loaded modules. There you can also see the file path of the Steinberg Runtime module. Make this module unavailable before starting Cubase, and the slowing effects are gone.
Ok, tried but couldn´t find anywhere in taskmanager, registry or services. I hope that this will be fixed by SteinbergASAP. Clocked my cubaseHub, took 25 seconds to load, not acceptable. Thanx anyway
This is a .dll that is loaded by Cubase as a dynamically linked library at runtime. I would advise against removing that without knowing what exactly it is good for and what possible side effects it can have. It is definitely a case of “warranty void if seal broken”.
If people want to try this, be sure you keep a backup of that file. Maybe it works without problems, maybe there are side effects.
Edit: seeing as this is in “common files “, it might also be that other Cubase software uses this dll (like Dorico, Wavelab or even Activation manager). Just be aware of that if suddenly some other programs don’t work correctly.
Well, after deleting the .dll file the result is the same, slow hub start about 25 seconds so there must be some other issue? Steinberg please look into this asap.
