Another JP plug-ins issue

Well it's probably related because almost every single plugin issue with JP has been Waves.

I think if the DLL isn't a VST it should not be in your VST scan path. Are you installing everything into one folder? Probably need to check the files paths when installlng waves?

Thanks Doktor. I saw there was a plethora of Waves/JP issues, but not quite like this.
During the scan the Sonar pop-up asks for the location of Waveshell-VST 9.3.dll, with a directory dialogue box for selection. 
I tracked the file down to C:\Program Files(x86)\Cakewalk\Vstplugins, and selected the directory, but Sonar blinks and repeats the pop up and dialogue box.
If I cancel out of this it continues scanning until it requests Waveshell-VST 9.3_x64.dll (is in the C:\Program Files\Cakewalk\Vstplugins directory).
So - are these the VST dlls? I thought Waves did things in a rather strange way, and don't use discrete dlls for each VST? My scan path includes these directories, so should I remove these paths (if so where are the Waves VSTs and how are they detected?)
 
Thanks
jdf
 
 

Thanks for the replies. I've seen the Waveshell-VST 9.3_x64.dll in the list and excluded it , but still can't get the scan to complete without the request for the waveshell locations, and the vst don't register. 
 
I've completely uninstalled Waves and reinstalled, but no progress there either. 
 
I saw the other thread on missing dlls in JP, and the exchange between Doktor and Noel.  Doktor is right - we need a more verbose scan method.
 
jdf

Noel Borthwick [Cakewalk]
>>Well it's probably related because almost every single plugin issue with JP has been Waves.

That doesn't help solve the users problem. If you don't know the answer to a problem its better not to respond than to mislead someone with speculation.

Noel first this really isn't speculation. We've just seen a flood of waves threads created here after Jamaica update.

Secondly what's is wrong with saying this? How does this mislead anybody?... Into doing what? Formatting their hard drive? What is inaccurate about this statement? Ironically you then continue to give advice specific to waves.

Thirdly you split my quote in half, making it look like that is all I said, making it look like a quip, the part you removed was my actual advice.

""I think if the DLL isn't a VST it should not be in your VST scan path. Are you installing everything into one folder? Probably need to check the files paths when installlng waves?""

I don't claim to come up with immediate solutions straight away, often I'm just trying to see if I can understand more of the issue and rule things out. Sometimes it can take two or three posts.I also don't claim to be perfect either. Sometimes (very often I suspect) I make mistakes.

If you don't want me to try and help people out in these forums anymore that's fine I think I get the message. I found your comments were pretty blunt and borderline rude. A mistake I often make BTW.

Please remember I am a customer as well, not your employee.
Thanks.

When this problem occurs the solution is to delete

C:/User/appdata/Roaming/Waves

Waves tech support are very quick to answer problems of this nature. That's how I got this solution. So in future with similar problems why not try Waves support.

stlstudio
All of my waves plugs are version 9.3 & I don't have past versions because I didn't start buying waves until version 9.3. I have a huge investment in them and they have become a critical part of all my mixes.
Waves Saphira disappeared after Jamaica update. I rescanned and it hung on waves CLA3a which is one of my favorite compressors & is in many of my mixes. I unchecked "rescan failed plugins" in scan options/reset/rescanned/ & then all waves plugins scanned properly. I've been using Sonar since it came out but any DAW that is going to give me hassles with my thousands of dollars in waves plugins is done. I don't have time for that. I didn't have waves problems prior to Jamaica.
 I'm on Windows 7 64 bit.

Did you try Mudgel's and Noels advice?

The issue may have started with JP but nothing here is pointing to a Sonar issue. Otherwise I would expect non Waves plugins to go tits up as well.

It may be an inconvenience but that doesn't change anything. You cannot conclude which party is at fault just because it worked before... However everything I've seen is pointing towards Waves. Others seem to be resolving their issues. Cheers...