chris.r Posted January 12, 2021 Share Posted January 12, 2021 I'm dropping a single VST3 plugin file into the default VST3 folder then Cakewalk scans and reports 2 new plugins added. Adding VST2 plugins works as normal. I have only default paths, nothing added there, no 32-bit folder as well. Anybody had that issue before? Link to comment Share on other sites More sharing options...
Bruno de Souza Lino Posted January 13, 2021 Share Posted January 13, 2021 Which plugin ? Link to comment Share on other sites More sharing options...
chris.r Posted January 13, 2021 Author Share Posted January 13, 2021 Any. Doesn't matter. Link to comment Share on other sites More sharing options...
Chris Boshuizen Posted January 13, 2021 Share Posted January 13, 2021 I try hard to only install VST3s, are you unchecking all the others when you install? Link to comment Share on other sites More sharing options...
chris.r Posted January 13, 2021 Author Share Posted January 13, 2021 If I install both, VST2 and 3, I get 3 new plugins reported by the scanner. If I only install VST2 then it does say 1 new plugin. Only when I install VST3 it tells me 2 new plugins (or 3 if I do both versions), even if I manually drop just a single file into the folder. That tells me the issue is only with VST3 for some reason. It just started yesterday, for years it was all ok. Link to comment Share on other sites More sharing options...
Kurre Posted January 13, 2021 Share Posted January 13, 2021 Only thing i can come up with is if you have a download folder for vst3 only. And that folder also got added to the scan path. Link to comment Share on other sites More sharing options...
Michael Vogel Posted January 13, 2021 Share Posted January 13, 2021 As an example, Waves install a mono version and a separate stereo version of plugins that have a Mono and Stereo operation, resulting in 2 plugins when you'd think that there'd be just the one as most other vendors do. Could it be something like that. 1 Link to comment Share on other sites More sharing options...
chris.r Posted January 13, 2021 Author Share Posted January 13, 2021 Thanks for help everyone. No, I only have the two default scan paths, one for VST2 and one for VST3 folder, both left untouched. I can do manually place a simple single-file *.vst3 plugin in the VST3 folder, no wrapper, nothing special just any simple plugin, and Cakewalk sees 2 plugins added. That only shows how bizarre things turned here with the scanner. Thankfully I can use the plugins without problem. One thing I noticed is that after updating a bunch of Plugin-Alliance and AAS plugins the scanner suddenly performed a full scan out of itself without me asking for it. Today I have found out that for some reason (or maybe it was me paying not enough attention) the AAS installer had changed the VST2 folder path during the update and I ended up with having two sets of AAS plugins, one in the main Vstplugins folder and another in an 'Applied Acoustics Systems' subfolder, will have to clean that up now. But, I've also checked and it didn't double the VST3 versions. Link to comment Share on other sites More sharing options...
Glenn Stanton Posted January 14, 2021 Share Posted January 14, 2021 hmmm, in the open project plugins browser, sometimes i see both the 32-bit and 64-bit versions get installed and i usually find the 64-bit ones listed in the appropriate category (not all the times) and the 32-bit versions listed in "uncategorized". Link to comment Share on other sites More sharing options...
Kurre Posted January 14, 2021 Share Posted January 14, 2021 Right-clicking on a plugin in the browser will give the option to put the plugin to a certain category/categorys. I have some that i marked for two or three categorys and they show up at every category they've been added to. Default should be no category selected and it goes to "uncategorized". Does the double plugin show in the filemanager where you start a manual scan? Link to comment Share on other sites More sharing options...
Bruno de Souza Lino Posted January 15, 2021 Share Posted January 15, 2021 On 1/13/2021 at 9:38 AM, Michael Vogel said: As an example, Waves install a mono version and a separate stereo version of plugins that have a Mono and Stereo operation, resulting in 2 plugins when you'd think that there'd be just the one as most other vendors do. Could it be something like that. You often have three: Mono, Mono to Stereo and Stereo for every plugin. Link to comment Share on other sites More sharing options...
Noel Borthwick Posted January 16, 2021 Share Posted January 16, 2021 VST3 plugins can be shells. A single dll can store one or more plugins so it really depends on which plugin you installed. Link to comment Share on other sites More sharing options...
Kurre Posted January 16, 2021 Share Posted January 16, 2021 I've read somewhere that sometimes one can rename the extension "vst3" to "dll" and use it as a Vst 2. Have not tried it myself but shouldn't hurt to try. Either it work or it doesn't. Link to comment Share on other sites More sharing options...
msmcleod Posted January 16, 2021 Share Posted January 16, 2021 7 hours ago, Kurre said: I've read somewhere that sometimes one can rename the extension "vst3" to "dll" and use it as a Vst 2. Have not tried it myself but shouldn't hurt to try. Either it work or it doesn't. A vst3 plugin is actually a DLL, but renaming it to .dll won't change the fact it's a vst3 plugin. It might fool some DAW's into thinking it's a VST2, but I doubt it'll work - the API's are very different (unless the developer for some reason decided to support both API's in the same plugin... if that is even possible) and there's a high probability it'll just cause your DAW to crash when you try to use it. 1 Link to comment Share on other sites More sharing options...
Noel Borthwick Posted January 16, 2021 Share Posted January 16, 2021 Changing the extension wont do anything. We look for the signature of the VST which is very different for VST3. Link to comment Share on other sites More sharing options...
Kurre Posted January 16, 2021 Share Posted January 16, 2021 3 hours ago, msmcleod said: A vst3 plugin is actually a DLL, but renaming it to .dll won't change the fact it's a vst3 plugin. It might fool some DAW's into thinking it's a VST2, but I doubt it'll work - the API's are very different (unless the developer for some reason decided to support both API's in the same plugin... if that is even possible) and there's a high probability it'll just cause your DAW to crash when you try to use it. Aha, that rings a bell. I think it was a plugin developer i got it from. Because he suggested to do that if there was problem with the vst3. He then obviously had made it with two api's. Ok, good to know. One thing less to test. I had probably done a test myself if it weren't for this new info. The developer never explained the double api thing. Link to comment Share on other sites More sharing options...
chris.r Posted January 20, 2021 Author Share Posted January 20, 2021 (edited) So exploring things further I narrowed down the issue is only with the vst scanner, both the browser and the plugin manager are counting plugins correctly. Some plugins, like the AAS Session series, are reported as 1 plugin but most that I have tried are counted twice by the scanner. Let's take a single plugin TAL Reverb 4, you can download the zip file here https://tal-software.com/products/tal-reverb-4 and just unzip the vst3 file from it and manually drop it in your VST3 folder (mine is standard Progam Files\Common Files\VST3). Before I did my plugin count was: vst scanner: 385 plugins found browser: 208 plugins plugin manager: (VST3) registered plugins 139 after I dropped TAL Reverb: scanner: 387 plugins found (1 new, 0 removed...) browser: 209 plugins plugin manager: (VST3) registered plugins 140 If I remove the plugin, scanner says: 385 plugins found (0 new, 1 removed) The blue toast notification after the scan was the only thing I paid attention after adding or removing any plugins, this way I have found out this behavior. Like I said, luckily there are no other issues with using my plugins only the amount displayed could be very misleading. Any technical explanation due to API etc doesn't make it, I'd like to see that I'm adding 1 plugin when I'm adding one plugin. Edited January 20, 2021 by chris.r Link to comment Share on other sites More sharing options...
chris.r Posted March 12, 2021 Author Share Posted March 12, 2021 To follow up, I just had a Cakewalk crash when trying to load Waves EchoSphere. Upon the next Cakewalk launch vst scanner told me I have one (1) plugin less than I had before crash. The EchoSphere is still there and working fine. Go figure out. ? Link to comment Share on other sites More sharing options...
Starship Krupa Posted March 14, 2021 Share Posted March 14, 2021 On 1/14/2021 at 12:56 AM, Kurre said: Default should be no category selected and it goes to "uncategorized". Actually, I believe that the VST spec allows developers to declare the category, which a host can query. Cakewalk is the only program I've seen that bothers to query and sort accordingly. Link to comment Share on other sites More sharing options...
lapasoa Posted March 14, 2021 Share Posted March 14, 2021 On 1/13/2021 at 1:38 PM, Michael Vogel said: As an example, Waves install a mono version and a separate stereo version of plugins that have a Mono and Stereo operation, resulting in 2 plugins when you'd think that there'd be just the one as most other vendors do. Could it be something like that. The same happens to me with Waves Tune. I have 4 plugins. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now