I don't think this is related to other current threads:
 
I have Waves JJP Bass and Linear Phase Multiband, and have been working well.
After updating to Jamaica Plain I rescanned VSTs.
The scan stalls at IDR - which I understand is Waves dithering element (and not a separate plug in)
I uninstalled Waves, reset and then rescanned VSTs
Re installed Waves, but still hitting the IDR problem and stalling the VST scan 
 
Has anyone any thoughts on this please?
 
jdf

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?

All my waves stuff (heaps) scans without issues, all seem to work fine, tested a couple of songs that use waves stuff pretty heavily, although I use another DAW now, don't really use Sonar anymore, but I keep it updated and test  things out.
I believe I read somewhere recently where one of the Cakewalk people mentioned that the done something which had to do with scanning/using whatever, products like waves that use a 'shell'.
 
Here it be http://forum.cakewalk.com/FindPost/3304879

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
 
 

I had the exact same problem except Sonar was hanging on Waveshell-VST 9.3_x64.dll instead of VST 9.2, and I ultimately clicked "cancel" after getting tired of the Explorer box reappearing even though I had correctly identified the folder where the DLL file was located.  I also noticed that right after canceling that Sonar loaded the VST 9.3 DLL, and I ultimately solved the problem...
 
Assuming I did not need the 9.2 version, I went into the Plug-in Manager and and removed all Waves plug-ins from my personalized grouping I had created, reloaded on 9.3 versions, and then excluded 9.2 versions one-by-one.  That did not work by itself; ultimately,  Sonar actually added "Waveshell-VST 9.3_x64.dll" as a listed plug-in in the list of choices, I excluded it, and then scanned and everything worked fine.
 
YMMV but hopefully this helps.
 
Steve

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

>>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.
 
>> 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. 
 
This is almost surely an authorization problem. Please check if you have obsolete waves dlls in the scan path and remove them. In the past errors like this may not have been caught. 
I have Waves VST2 and VST3 plugins in my path and there are no problems scanning them.
Also if you think the scan appears to be hanging check to see if there is a popup window from Waves telling you it is not authorized. You can also contact Waves with auth issues or check your Waves licence manager to see which plugins are indeed authorized.
 
>>we need a more verbose scan method. 
You can capture a scan log by shift clicking the Scan button in preferences VST. Although that contains a lot of technical information that is more useful to support than end users.
 

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.

OK - I've sorted it now. I uninstalled all Waves and trawled through the vst paths to clear any stuff out.  All I found was (I presume an erronious) a redirect shortcut in the ProgramFiles(x86)/waves/plug-ins v9. I scanned again; WaveShell-VST3 9.3_x64 still threw upo the dialogue to locate the directory; so I had to manually steer each waves plug in through to ProgramFiles(x86)/waves/plug-ins v9, and all plug-ins have now appeared and functioning.
 
Thanks to everyone for your input.
Noel - as CTO on a Saturday afternoon (evening here in UK) .. that's dedication yet again!! Thanks.
Dok and everyone else - thanks also for you guidance
 
Jerry
 
 

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.