Hi Paul, is this problematic in your opinion>
“Updating cache files
Finished 747 plugins, (873 ms - average 1 ms)
vstscannermaster OK”
VST2 scanning is where my issue seems to be, however, it doesn’t seem to be a problem with WaveShell, according to my untrained eye…
It shows:
“Scanning: WaveShell-VST3 9.2_x64 (743/747)
Scanning: WaveShell-VST3 9.2_x64 OK (477 ms)”
Any suggestions based on this?
Thanks…
Deactivate VST2 support for testing.
If it is an VST2 plugin, find a VST3 version of that plugin.
For Waves plugins, you can go to troubleshooting steps on their website.
The current logging is only implemented for VST3 plugins. The VST2 scanner is a different component that works in a different way. If Cubase is slow to start up because one of the VST2 plugins is hanging then check the process list in Task Manager (win) or Activity Monitor (mac) – you’ll probably see a vst2xscanner process. You can kill that and (in theory) the plugin should be put on the block list so Cubase will continue to start up, and will be ok to start next time.