• SONAR
  • Solved-Plug-in manager can't find my new Wave plug-in--first time this problem
2016/03/17 09:41:10
michael japan
I have recently left my old company and had to (wanted to) purchase a lot of the waves plug-ins as the plug-ins were part of my old work. Up until now everything has installed fine but the latest purchase-Maserati GRP. I have all my licenses of course going through Waves Central and have moved all licenses to a USB drive. Waves Central says the drive is there.
 
I am not new to the Plug-in manager and have "added" about every folder that I can think of that would house the new plug-in and re-scanned but to no avail.
Where is the little sucker? How can I locate it?
 
Sigh--10:40 pm and hungry.
I hate going to bed with things like this hanging in the air. It's easy for me to leave my work until the next day, but technical issues drive me up a tree--maybe I'm a bit nuts but hey.
 
Thank you everyone.
Michael
2016/03/17 10:14:26
dcumpian
You only need to have Sonar scan the Waveshell DLL. I haven't had any trouble with Waves VST3 versions, so you might just scan that DLL and rename the VST2 just in case there is a conflict.
 
Regards,
Dan
 
2016/03/17 10:24:26
michael japan
thank you. Actually, what I did was re-install them all through cloud instead of using the licenses off my usb drive and it found it. Dan, so you just scan the one waveshell DLL? There isn't answhere where the plug-ins are listed by name. An yes, this is the first problem I add. It's like it was licensed but not installed--if that is possible. Anyway, going back and re-installing them all online did the trick.
 
2016/03/17 15:22:52
Zargg
Thanks, Dan. I experienced this today myself (bought and installed IR1 earlier today), and was looking for an answer right now.
All the best.
2016/03/18 10:59:58
dcumpian
michael japan
thank you. Actually, what I did was re-install them all through cloud instead of using the licenses off my usb drive and it found it. Dan, so you just scan the one waveshell DLL? There isn't answhere where the plug-ins are listed by name. An yes, this is the first problem I add. It's like it was licensed but not installed--if that is possible. Anyway, going back and re-installing them all online did the trick.
 




Yes, just the VST3 waveshell DLL is all you need. I also installed the 64bit VST2 DLL, but I renamed it so Sonar wouldn't try to load it. It's there if I ever run into a problem with a VST3 plugin, but so far, I haven't had to use it.
 
The actual plugins are stored elsewhere, but the waveshell loads them, not Sonar.
 
Regards,
Dan
2016/04/19 01:09:21
michael japan
having the problem again with a new plug. I can see the .dll when going through my c:drive but for some reason when scanning it can't find it--keeps going to documents and I can't navigate to it. Have contacted waves. I have moved my licenses back and froth to the cloud and back to usb but maybe just don't really understand. Sorry to be so dumb in this area.
 
2016/04/19 02:46:07
The Grim
i have come across this a few occasions when adding a new plugin, it would not show as available in the list, what i do is remove the path from sonars vst scan path in preferences, close it then re add the path and it re scans and all is good. a simple re scan would never do it for me but when it happens the above works for me every time. same thing happens in reaper when i add a new waves plugin, it doesn't show up and in reaper i just clear cache and rescan and all is good. i never experience the issue in studio one
2016/04/19 03:55:42
michael japan
thank you--tried that but it keeps looking for it under documents no matter where I put it, and then when I navigate to that folder through the vst scan it can't find it, even though when I open my c:drive in explorer I see it there. Very strange.
2016/04/19 04:35:58
The Grim
is the vst3 waves shell in your program files\common files\vst3 folder?
 
are you moving things around from where waves central put them? it's been a long time since i originally installed waves first up, i can't recall if you have any options, but i would have just let it put things where it wanted. i think vst3 defaults to program files\common files\vst3 folder and perhaps 'has' to be there.
one thing i know is that if you are having problems, in the 1 or 2 times i have contacted waves support they have been very helpful, very fast, and very professional, no doubt the best support i have experienced by far, not that i have experienced a lot, but still
2016/04/19 04:55:55
subtlearts
I have had recurring issues with new Waves plugins, especially when I have had the demo installed and working to check it out first. So far the only thing that works is uninstalling and reinstalling all Waves plugins. I have been able to do this directly from the Waves Central app, without doing backflips to clean the registry or anything, just a simple uninstall all and reinstall all, and then Sonar is able to find them somehow. Possibly there is a cleaner, more elegant, less brute-force method, but I haven't found it, and I've tried quite a few things. This one seems to work, as ugly as it is... 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account