It would be a nice option to disable VST scan at startup…then maybe the application would initialize in less than 10 seconds.
5 Likes
If I look at the start process here, plugin scanning is not what takes an immensely long time, compared to the rest of whatever Cubase is doing… would still take 30, 40 seconds without it,
The bigger problem is that their support and/or this forum will be flooded by “bug” reports from users à la: “I installed this and this plugin and it is not showing in Cubase”.
A better solution would be to do the plugin scanning in the background, like e.g. Cakewalk does.
2 Likes
I agree, sandboxed vst scan process is a good Idea. Currently, when Cubase finally does initialize, I’m no longer in the mood to make music.
2 Likes
I Totally Agree with all of you guys and it is about time cubase engineers start solving this big heck
1 Like
I hope this doesn’t upset any Steinberg employees, but I feel this disable (or sandbox) option needs to be instituted for those of us who work with a lot of plugins - I do research on music software and need the plugin library that I have. And I rarely use Cubase at this point because of being punished for having a large plugin collection. Just now I was using FL Studio and I inadvertently clicked on a vst3 download (that was purported to be an .exe - I should have looked before clicking. Well, it seems that Cubase hijacks vst3 so that when you click on it you get trapped in a 5 minute error prone Cubase plugin even when you’re not using Cubase.
In FL Studio image line have created a “fast scan” option, so that the user is never forced to scan. If they want to use a new, unscanned plugin they have TWO options. They can either do a fast scan and then manually categorize the plugin (Synth or FX), or they can run the full scan, at a convenient time when the PC is not in use. I rarely get errors. In the case of Reaper I DID get errors, more so than even Cubase, but at least with Reaper you can give it every path (like FL Studio) and temporarily remove paths you feel may be generating errors. I don’t think Cubase has this capability of limiting plugin paths… They seem to be recommending a single VST 2 and VST 3 path, so I don’t imagine they offer this option of debug where you CHOOSE which locations you want scanned.
My bottom line is I think they should at least let us decide IF we want to scan when launching. More ideally they could additionally let us have the 2 levels of said scan as offered by FL Studio, AND let us choose and change (for debugging) which folders to scan.
It’s 2024 and I’m still waiting for Cubase to open…
1 Like
Indeed. A simple flag setting in the Preferences that defaults to On. Then us pros, ahem, can turn it on when needed. Bearing in mind that a scan can be initiated in the plugin manager.