Hello Cubase Forum,
I am looking to switch to using Cubase as my main DAW but I am running into issues when scanning VST3 plugins. I am using a fresh install of Cubase. I have never had it on this machine before. When scanning VST3 at start up, the app becomes unresponsive and I see in the activity monitor that the plugin scanner uses 100% CPU.
Can anyone give me advice on this?
Hi and welcome to the forum,
Does it really crash? Do you get the *.ips file? Or does it freeze?
Mac: macOS Console utility > Crash Reports (or ~user/Library/Logs/Diagnostic Reports).
Hey there Martin.
Unfortunately, there is no crash log, so it is only freezing. I spoke to a support tech today who said that I would have to delete and reinstall all of my VST3 plugins and figure out which one was freezing the machine, but that is just not an option. I have way too many running projects/sessions and thousands of plugins. (I am a mix engineer who works directly from production sessions)
Do you know how I can troubleshoot this without deleting and reinstalling all of these plugins?
(One other thing. I have already refreshed the preference, made sure that I deleted all demos, and Cubase DOES load up when disabling plugins.)
Hi,
You don’t have to uninstall the plug-ins. Just remove the *.vst3 files from the given folder, to find out, which plug-in is faulty. Use the Binary search algorithm.
Somehow, that worked, and I didn’t even have to delete any plugins. Very weird.