The culprit was a seemingly inoffensive (Windows) shortcut that he placed in the VST3 folder (“C:\Program Files\Common Files”). I had to do this with the SIR Audio Tools plugins. So for this I thank you, Booli! Too, if you are still confused about where a plugin is stored, you can reinstall it and it will typically ask (or tell) you where the plugin is going to be installed. OK, that’s what I did and everything is running much better than it did, you can feel the communication process between Cubase and the various plugins is way better, I’ve never had things running this quickly before. I will add that concerning the plugins from SIR Audio Tools (I have 4 total), 3 actually use the VST2.4 version, there is not a VST3 labeled version available for all 4 plugins in other words, only 1, the Spectrum Analyzer. If it did I continued down this path, removing all the VST2.4 plugin versions that had a VST3 counterpart. If It was still there, I opened the project and tried the plugin to make sure it would work. Then I opened the Plugins Manager (in my Project) and searched for the plugin using the Plugin Manager Search window. (It turns out that Cubase will always use the VST3 version when it has a choice.) When I found these files - and there are many, some stored in places BESIDES the Common Files > VST3 Folder - I closed my Plugins Manager window, created a desktop folder and dragged these possible VST2.4 plugins into it, starting with one.
Cubase 3 vst .dll#
dll file, they are self contained it seems.īacking up a bit, to discover where these VST2.4 plugins were located, I opened the Plugin Manager in C10 found and clicked on the particular version, noted where the file was located, and then opened the VST2.4 plugin location (But only WHEN THERE WAS A DUPLICATE VST3 version listed!). But for other plugins this is not the case, they can operate without the. FOR EXAMPLE: iZotope will show both of these files - and - more importantly, they must both remain for the plugin to work in the C10 WL domain. dll files and also ‘VST’ labeled files here of the same program. My Waves plugin shells were here, as well, but not in a folder). Within my Win7 64bit OS, most of my add-on VST plugins were located here: C > Programs > Common Files > VST3 > (Folder with name of Plugin Manufacturer, in my case: Celemony, HOFA, iZotope, SIR Audio Tools, etc.
![cubase 3 vst cubase 3 vst](http://blog.landr.com/wp-content/uploads/2016/06/0001_FuzzPlus3.jpg)
And more interesting is the fact that the Steinberg Plugin Manager records/displays both of these installed versions in it’s listing, but doesn’t necessarily use the VST2.4 version WHEN the VST3 version is available… WHEN the VST3 version is available. Remember here that VST2.4 CAN BE A VST3 PLUGIN, keep this in mind.
![cubase 3 vst cubase 3 vst](https://i.ytimg.com/vi/xwMB_kd7rno/hqdefault.jpg)
Well it turns out that this is exactly what happened - ALTHOUGH THE PLUGIN MANAGER CONFUSES ME HERE - because the creators of my plugins offer TWO VERSIONS OF the SAME VST3 PLUGINS: VST3 and VST2.4.
![cubase 3 vst cubase 3 vst](https://www.espace-cubase.org/newcub27a.jpg)
I always have done this - so it would be logical that nothing but VST3 plugins were installed.
Cubase 3 vst Pc#
I have always, on plugin install, unclicked every version that will be loaded onto my PC EXCEPT VST3. Moving on, key for me was using the Plugins Manager in C10 and finding where the various plugins were stored - BUT - also REMOVING THE VST 2.4 versions WHEN THERE IS A VST3 COUNTERPART VERSION AVAILABLE… Let me explain this last remark.
![cubase 3 vst cubase 3 vst](https://musictech.com/wp-content/uploads/2020/09/Cubase-VST-copy@1400x1050.jpg)
OK, before I begin, I realize every OS is different so what and where I changed things may be more (or less) complicated. All I can conclude is that Cubase and WLPro were spending a lot of effort locating every possible VST plugin. It opens very quickly now and closes qickly as well, plus, my ‘Other’ folder within the plugins list was reduced by 75% as these redundancies were eliminated. First off, let me thank you for sending me down this rabbit hole - seriously - because it has really transformed the operation of C10 and WLPro.