Hi
Thanks for all your reports. I will discuss with the team to prompt more granular information at this stage of the start-up of cubase.
Cheers,
Armand
1 Like
went through this nightmare for the last 2 hours, turned out to be one plugin causing the issue, rhodes vpan in this situation , what i did was take all vst3ās from the folder and place in a new folder on desktop, then i put them back a few at a
time, as i have too many to one at a time, and a process of elimination brought it to the vpan, uninstalled and works fine now , shame coz that was a cool plugin, maybe rhodes will fix it soon
100%, this: itās happening to me right now.
Steinberg needs to get it through their thick heads that they will be hemorrhaging lots of customers if they donāt get on top of their own silly VST3 plugin format being able to destabilize Cubase so badly. There is simply no excuse for this.
We canāt be expected to point the finger at Waves or NI or ANYONE else but Steinberg here: itās their DAW, itās their format, and it is their responsibility to ensure that old software cruft from perhaps dysfunctionally run plugin development houses (NI, Waves are great examples) cannot bring the entire DAW to its knees.
If there is a problem, Cubase needs to be savvy enough to detect and disable, as needed. For chrissakes, this is exactly what machine learning is for!
Weāve put up with software too dumb to manage itself long enough: itās a new age, a new era, and we need the necessary intelligence built into the code to ensure that it can notice and do something about these such issues on its own so that we donāt have to spend all our valuable music making time shouting into the void in internet forums, because it will always, always be something new! Some new stupid failure scenario will always crop up because Steinberg is simply not focusing on the things it really needs to and they keep releasing software, anyway.
This program is a nightmare. I got a little done today before yet another Cubase 13 crash that was triggered by that intensive operation of switching over to Chrome and then back to Cubase. I know, I knowā¦ itās a lot for a DAW to handle, go easy guys!
This is definitely a great idea. Our aim is to ensure a better decoupling between the DAW and plug-ins in the future. That besides this problem has to do with regular process management and not machine learning.
Please send me any IPS / DMP in PM in this regard so that we can investigate further and potentially find a work around for this issue.
Cheers,
Armand
1 Like
Cubase 13.0.20 64bit 2024.1.11 18.33.50.856-freezedump.dmp (2.5 MB)
Thanks for taking my issues seriously; that is at least encouraging. But, I think machine learning could be invoked more to detect hardware/software commonalities between users and alert them that, e.g., Windows 10 doesnāt know what to do with gen 13 & 14 Intel Core i9 process scheduling for real time audio but Windows 11 somehow does.
But I think it could go much, much deeper than that in terms of the program itself detecting anomalies and pointing out likely or exact culprits. Inbuilt crash dump analysis and even taking action on its own, perhaps with user consent when appropriate.
This may take a while to get right and for it to be truly useful, but from what Iām seeing in my space, itās far from impossible. We really are at the start of a technological revolution thatās going to change damn near everything. Most unsettling and yet most interesting thing perhaps in history, all at once.
I strongly think Steinberg should implement a time-out in their VST3 checking software if this is still happening (to be it was happening in Cubase 11 but not 12). Because it seems bizarre that if there is an issue with one plugin the whole software stops working.
In my case the problem seemed to be with a Rhodes plug-in (V-Pan).
For people coming over this feed the way I discovered it was to go in the Common Files/VST3 folder, take out everything and save it in a different folder and slowly introduce things, open Cubase, close it, introduce more VST3, repeat. To fasten things up I put things back alphabeticallyā¦ Thatās how I found the problem was with a plug-in that began with V, and then for those ones I did the operation one by one until I found that the issue was with V-Pan (lucky for me I only had 2 plugins starting with V).
The fact is that if there is an issue with a VST2, Cubase puts it in the blacklist and keeps goingā¦ why it doesnāt do the same for VST3 plug-ins is beyond me, but you would expect it to happen from a top producer like Steinbergā¦ Error handling and time-out is coding 101 to not get software stuck.
2 Likes
Itās 07-2024 and I am having this issue after an update to Cubaseā¦
Why wouldnāt these problems be resolved by now?
We should not have to be computer forensics scientist and musicians too.
2 Likes
I have killed in task manager the stuck VST/license check process, next time the program started OK
I discovered later that V-Pan needed another piece of software to run in the background and I had killed it (CodeMeter, it is used for licensing). Reinstalling allowed to reset the settings. So, once you found the problematic plug-in, if you need it, also check stuff like this in the manual or webpage, or with the manufacturer. You might be able to solve the issue and thence start using the problematic plugin again.
Hello all
I have been a long time user of Cubase and for the 1st time I also saw this issue of getting stuck at the intro box saying āscanning VST3 pluginsā. This happened on my new Macbook Pro M3. I have Cubase 13 and I recently installed the V15 version of plugins of Waves.
After going through all the above messages in the thread, it seemed that Waves is the main culprit here. So I tried that first as a solution. I completely uninstalled all the VST3 plugins of Waves from my Macbookā¦and VOILA!!! Cubase is back to itās glory. So based on my experience I can very confidently say this issue is because of the one and only āWavesāā¦!!!
I just started having this problem. Totally out of the blue. I replaced another hd that has NOTHING to do with VST3 and after re-starting the problem began.
Iāve gone so far as to remove all VST3 files and re-add one by one. Iād like to blame it on Waves, but itās NOT just Waves. After re-adding some plugs just zip by, but othersā¦ including Native Instruments I believeā¦ ALSO cause the hang.
=Eventually= it loads (20 minutes!) But if I disable the Scanner to get past that the plugs are unavailable.
I also tried reverting to Cubase 13 and it has exactly the same problem. Obviously using the same VST3 Scanner. Arggggh!
And the REAL maddening thing? It happens EVERY time! The Scanner isnāt even smart enough to blacklist bad plugs. So EVERY startup is like this.
Any ideas?
I will say that Cubase needs to fix thisā¦
There is no reason that in edition 14 that we should have this problem.
It should not matter what the VST is, Cubase needs to figure this one out and fix it.
It is July 2025 and this is still a problem.
I upgraded to 14 and I seem to have mild issues with starting up. I am on the 14.0.32 and it is now taking me over 30 minutes to start Cubase after booting my PC.
If I close Cubase after the first start, and restart Cubase, it only takes about 5 minutes which is still too long.
Cubase, cut it out, fix the problem, or tell us what to do.
I know these treads are monitored because you once banned me for trying to get the community to help me when you wouldnāt.
I am beyond frustratedā¦
1 Like