I installed the free Plugin Alliance plug-ins and after running Cubase Elements 14, it already takes two hours to scan VST3. How to solve this problem?
It shouldn’t take that long.
Can you be a it more specific about your system and OS?
What kind of free Plugin Alliance plugins are we talking about? Can you name them, please?
Windows 11 Home 24H2
free plugins of Plugin Alliance
PA FREE (19/19)
bx_blackdist2
bx_bluechorus2
bx_boom!
bx_cleansweep V2
bx_distorange
bx_greenscreamer
bx_masterdesk Classic
bx_megasingle
bx_metal2
bx_meter
bx_opto Pedal
bx_rockrack V3 Player
bx_shredspread
bx_solo
bx_subfilter
bx_tuner
bx_yellowdrive
Free Ranger
niveau filter
installed as VST3
Can you actually see it still scanning or has it maybe just frozen?
If there’s nothing moving I would force quit and try again…also did you let the installer install these to the default location? They should be in program files/common files/vst3.
The search is still active. In the task manager, the CPU power used changes so I conclude that the application is still active, just hovering on something. The files are in the correct location. In the application window the message: initializing scan for VST3. On the other hand, moving the mouse over the application on the taskbar a curiosity - a message: license checking
I don’t know if this helps but, Steinberg already issued an advisory about this.
However, Alliance plugins are linked to a Device and Machine ID. Check in your account under Mange Registered Plugins or Manage Divice.
Added exclusion of the C:\Program Files\Common Files\VST3 directory from security scanning. Did not help.
Here’s what I would try. Open the vst3 folder and move most of those PA plugs out on to the desktop…leave one or two.
Then try to start Cubase, if it completes scan , open the plug(s) and activate license (you have to log in to PA account).
If that all goes well try another handful.
I think I know what the cause is. Text from the Plugin Alliance website https://www.plugin-alliance.com/en/activation-manual.html:
“When you’ve installed your plugins, start your digital audio workstation (DAW) software. Most DAWs will wait until you instantiate a new plugin in a session before starting the activation process. In Pro Tools, a new plugin will produce the activation window during the plugin scan at startup. Pro Tools will incorrectly report that a plugin is invalid if you don’t complete the activation process at startup.”
The problem is with activating the licenses of downloaded and installed plug-ins. Cubase should trigger their registration. Unfortunately, something is holding up the process.
Like I said…It doesn’t ask for activation until you open the plugin.
Scanning worked fine here with one of these plugs…did you try my suggestion?
Just to give you a heads up. Following @Grim 's advice you might want to give them a short test ride and see if they do anything for you. I tried most of them out of curiousity as they came for free with a purchase and deleted almost each and everyone of them right away. However, you got to find out yourself which one floats your boat
That’s exactly what it was to test and learn about these extensions. No less, it may be some flaw in Cubase that is worth solving with some upgrade in the future.
No, I don’t think that Cubase is the culprit. I remember that there were absurd activation processes involved causing all sort of trouble. Because of that I avoid certain brands which are widely known to be troublemakers. Not just in Cubase.