cclarry Posted February 3, 2020 Posted February 3, 2020 PSA: If you have VST2 plug-ins please ensure that you do NOT install them to the standard VST3 plug-ins path. CbB from 2020.01 onward will no longer scan any .dll files placed in the VST folder. (Program Files\Common Files\VST3) If you have any VST2 plug-ins in the wrong path please move them to a different folder such as C:\Program Files\Common Files\VST2 and adjust your VST scan paths accordingly 3 4
scook Posted February 3, 2020 Posted February 3, 2020 I have seen a couple reports of Toontrack plug-ins in the VST3 folder. Have not determined how they get there but Toontrack does not make VST3 plug-ins so their stuff should be installed elsewhere.
Mesh Posted February 3, 2020 Posted February 3, 2020 14 minutes ago, scook said: I have seen a couple reports of Toontrack plug-ins in the VST3 folder. Have not determined how they get there but Toontrack does not make VST3 plug-ins so their stuff should be installed elsewhere. Yeah, I've noticed that they're installed there as well (via the Toontrack installer). However, I haven't had any issues when opening them from there.
scook Posted February 3, 2020 Posted February 3, 2020 As long as a VST reset is not run existing VST2 in the VST3 folder should work. If a VST reset is run, the registry entries will be removed and the plug-ins will be skipped during the scan. 3
TheSteven Posted February 3, 2020 Posted February 3, 2020 Is it safe to assume that VST3 plugins NOT in Program Files\Common Files\VST3 will not be scanned? I've seen a couple of plugins install their VST3s in their VST2 folder. It won't bother me either way because I move 'em if I catch that their not installing in the correct locations, but curious.
marcL Posted February 3, 2020 Posted February 3, 2020 But what's about the iZotope plugins? They come with a .vst3 file and a dll file starting with "i.....dll". Will they still run properly? ? It is always an annoying trap if some plugin providers tinker there own exotic solutions ? (like iZotope here, and especially Waves). I have separated all other plugins.
TheSteven Posted February 3, 2020 Posted February 3, 2020 iZotope has numerous helper dlls in the same folder that are not actual plugins - the scanner rejects them and moves on.
scook Posted February 3, 2020 Posted February 3, 2020 AFAIK, ALL files with vst3 and dll extensions in the scan path will get scanned EXCEPT in the dedicated VST3 folder where dlls are skipped as of 2020.01. The iZotope VST3 plug-ins all scan and load using the vst3 extension. The dlls are called from the vst3 files. For true VST2 plug-ins in the VST3 folder, it is possible to force them to scan in 2020.01 by adding a directory junction in the VST2 scan path. I would advise against adding the entire VST3 folder but adding specific folders like C:\Program Files\Common Files\VST3\Toontrack should be OK. IOW, running a command shell as administrator in C:\Program Files\Cakewalk\Vstplugins and typing mklink /j Toontrack "C:\Program Files\Common Files\VST3\Toontrack" I tested this by moving my Toontrack folder under the VST3 folder and it scanned OK. Still think it would be better to move/re-install VST2 dlls to a path outside of the VST3 folder though. 1
TheSteven Posted February 3, 2020 Posted February 3, 2020 11 minutes ago, scook said: Still think it would be better to move/re-install VST2 dlls to a path outside of the VST3 folder though. Ditto. Some vendors place their VST3 in subfolders in C:\Program Files\Common Files\VST3 I also use subfolders under ...\VST3 to organize my VST3s and reduce clutter. Not at home so I can't test if this a now problem.
scook Posted February 3, 2020 Posted February 3, 2020 Yeah, it is surprising how many dump their plug-ins in the VST3 root. I am a fan of dedicated manufacturer folders. 2
TerraSin Posted February 3, 2020 Posted February 3, 2020 16 minutes ago, scook said: Yeah, it is surprising how many dump their plug-ins in the VST3 root. I am a fan of dedicated manufacturer folders. I prefer everything being in one place. That way if I have plugins or programs that need to be pointed to the folder, it's only one instead of many
Paul P Posted February 3, 2020 Posted February 3, 2020 33 minutes ago, scook said: Yeah, it is surprising how many dump their plug-ins in the VST3 root. I am a fan of dedicated manufacturer folders. Acustica dumped a whole bunch of stuff into my vst3 folder
scook Posted February 3, 2020 Posted February 3, 2020 So does Arturia, AAS, Cakewalk, Plugin Alliance, Softube, u-he and Valhalla to name a few. And since the path is part of the spec, most of these manufacturers don't provide a way to override the default path.
user905133 Posted February 3, 2020 Posted February 3, 2020 (edited) Reply to the first post in this thread removed because this topic is being discussed elsewhere. Edited February 3, 2020 by User 905133 to remove my request for clarification because it is not about Deals.
Hidden Symmetry Posted February 3, 2020 Posted February 3, 2020 I was always told to never install VST2 into the Program Files\Common Files\VST. I didn't think it was possible or would work properly. Same with 32b & 64..never the same folders.
scook Posted February 3, 2020 Posted February 3, 2020 Most plug-ins work just fine in folders under C:\Program Files. The exceptions are plug-ins that write into the folder containing the dll. This is the case with a lot of plug-ins built with Synthedit. These plug-ins should be installed in an area where users have read/write access otherwise the DAW must be run as administrator.
jesse g Posted February 4, 2020 Posted February 4, 2020 (edited) Thanks for the news Larry!!! Edited February 4, 2020 by jesse g 1
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now