In the grand scheme of things, this is just a small (and hopefully one-time) annoyance. I'm assuming (actually, "hoping" is more like it) that everything will scan properly when I'm through but, as I haven't actually tried it yet, I can't say for sure. A word of caution about that last statement: I haven't tried relaunching the latest C10 or N10 yet, because I'm still looking for duplicates. and shuffle files/folders around as necessary.
#CUBASE 10 PRO PLUGINS WINDOWS#
It obviously pays to (determine where all of your plugins have been installed and then) check all of your plugin folders every once in a while - using Windows Explorer, it's a trivial matter to search for '*.dll' in the VST3 folder, and for '*.vst3' in every VST2 folder. I guess that's not much of a surprise, since it shows up as a 32-bit file (I also wish that there was a way - besides looking at the file extension, which may not always be indicative - to tell whether a particular file is 32- or 64-bit). and, when I tried to reactivate it anyway, I got the following error message: One really weird one is IRCAM's "The Snail" - the plugin itself is fine, but the accompanying "fft.dll" got blacklisted because it's 32-bit. I'm pretty sure that it at least used to work that way, but maybe things have changed.?. This would make sense, since we all probably have older projects that were created using the VST2 version of a plugin.
I believe that both the VST2 and VST3 versions of the same plugin should be allowed to work, side-by-side. so I manually deleted the VST2 subfolder, and then moved the VST3 subfolder to the appropriate place. I just discovered that Stagecraft Audio, for example, installs both VST2 and VST3 subfolders in the folder that I entered for installation of the VST2 plugin. There were a few VST2 plugins that were installed in the VST3 folder, and a few VST3 plugins installed in the VST2 folder.
I then started going through all of the various folders where plugins have been installed (I use my own dedicated folders for 32- and 64-bit VST2 plugins (although the installers don't always place them there) and, while most of the VST3 plugins are usually automatically installed in C:\Program Files\ Common Files\VST3, they aren't always. It took a long time to reactivate each plugin in each program, one at a time ( I wish that we could highlight a bunch of them and 'batch-reactivate'), but I just reactivated all of the 64-bit ones.
including plugins that were never blacklisted before. and everything from SoundToys, and everything from XILS Lab, and everything from Mercuriall Audio and Nembrini Audio, and about thirty other plugins. I just updated to the latest version of Cubase and it blacklisted Play.
0 kommentar(er)
