If I remove that plugin, it's smooth, otherwise it's clicking- almost like static.
 

Hi. Which latency setting are you using? It is a quite CPU hungry plugin.
All the best.

It's not a live play plugin. I only use it on muxdown when using onboard sound card. When I use the Digigrid DSP server it much more lean on CPU power.

One thing that might help is collapsing the gui to switch off the animation. That reduces cpu load caused by the plugin some.

Other than that, increase the ASIO buffer size. It's a resource-hungry plugin. It also adds quite a lot of latency itself as well, so isn't really suitable for use until after tracking has been done if you need to monitor through Sonar.

I have found very strange behavior from this plug in that has caused me to regret spending the money.
 
I can insert the plug in, and yes, while CPU hungry. It works fine.
 
Then if I save the project, close the program and reopen it, it pops like popcorn.  It's the only plug in in my arsenal I have such a problem with. And its not asio buffer... been there done that.  There's something wrong with the plug in.
 
I went to Waves to see if there were any plug in updates, and they make you pay for bug fixes after the first year.
 
I am so let down by waves in this regard that I will never buy another plug in from them.  And I have bought a number of them. But never again - sell me a defective plug in, and don't stand behind it unless you wring more money out of it, they can pound sand.
 
Rick

i have had no issues with the plugin, don't see it as especially cpu intensive, never actually had occasion to think it was more so than other plugins i have. great plugin, love it. (i use studio one 3 pro 99% of the time, sonar rarely)

No, I've had no issues with the plugin either, it works fine in Sonar (VST) and Logic Pro (AU) for me. It's a very nice plate reverb emulation indeed, but does use a lot of cpu compared to other convolution or algorithmic reverbs I use.

rickidoo
I have found very strange behavior from this plug in that has caused me to regret spending the money.
 
I can insert the plug in, and yes, while CPU hungry. It works fine.
 
Then if I save the project, close the program and reopen it, it pops like popcorn.  It's the only plug in in my arsenal I have such a problem with. And its not asio buffer... been there done that.  There's something wrong with the plug in.
 
I went to Waves to see if there were any plug in updates, and they make you pay for bug fixes after the first year.
 
I am so let down by waves in this regard that I will never buy another plug in from them.  And I have bought a number of them. But never again - sell me a defective plug in, and don't stand behind it unless you wring more money out of it, they can pound sand.
 
Rick

I have all the Waves plugins and find no problem with them or the Waves update program WUP.

Many/most plugins are updated yearly or there abouts and when they go to a major update number eg v3.1 to v4.0 then you'll have to pay an upgrade fee if you want it. If you don't your current version will still work and continue to work.

WUP is exactly the same, you can update or not, it's your choice. However if a new version is released during your WUP period you'll get it without any extra fee. At normal retail prices I have over $10,000 worth of Waves plugins and I just paid my WUP last week. Instead of the maximum of $300 I was able to get it at a discount for $193.08. and it won't expire until Feb 2019. I got nearly 2 years of WUP because of various overlap dates.

During the last year I received 7 new plugins that I didn't need to pay for as they became included in the bundles I owned.

As far as Waves support goes, it is about as good as it gets. I have never had to wait more than 24 hrs (I'm in Australia) for answers to any questions. Even had live links to work out something I had trouble understanding.

There have been occasions when Waves plugins have had problems but I've never know the company to not fix problems and work with DAW manufactures to sort things out.

Now to your problem with your plugin, how about some symptoms and let us know what your current setup is and lets starting working with some facts and we'll help you best as we can to fix your problem.

Oh and open your own thread so we can keep your problem clear of the Origonal Poster's. It's also consider poor forum etiquette to hijack another persons thread. Thanks.

Interesting.   This plugin does seem to work perfectly initially, and then pop on another day when the project is reopened.  
If I delete or turn off the plug, the popping is gone.  
I have a healthy buffer size, 1024, but I could try longer.

i have mine set to 128, no issues, again this is studio one 3 pro, rarely run sonar anymore, but i'll fire up platinum later and have a look see
 
[edit] just took it for a spin in platinum on an old project, 4 instances, 128, seemed fine there as well for me, no issues