Sonar's new mastering tools causing playback problems

I normally use Ozone and other Izotope tools, and I love them. They are supposedly CPU hungry, but my system runs well on them. However, the new Sonar mastering tools are completely unusable on my system, causing playback to stutter, lag, and get out of sync. Deleting the instance of the plug-in eliminates the problem.
 
Anyone else finding this to be a problem? I'd like to try and use these to see how effective they are, but I can't and I don't remember ever having a problem with a Sonar update or Sonar effects before.
 
 

I am having exactly the same problem with the new plug ins.  They cause shuddering during playback and drop outs. Like yourself I have never had any problems whatsoever with any sonar Platinum upgrade until this one. They look good and I would like to give them a try but at this time they do not work. Up until this new upgrade everything has been excellent.  How about some help here to get these things fixed.
Blackie

"nonlinear" worked for me, this was when I was using Addictive Drums, would drop out during a pattern play back. Review the first link above.

Not exactly the point of a linear phase EQ. 

thepianist53
 A "slim" edition with the cababilities and engine of the "bundled" version might be more cost-effective in the long run, as I have so many built-in options in Sonar that I simply do not use.
 

I think you just invented Sonar Artist.

What happens if you load up a simple stereo WAV in a clean, empty project, and slap the mastering plugs on the buss? Do you still get drop-outs and stuttering?

One should keep in mind that LP plugins should be use in the mixing or mastering phase. This also means one can up the latency so these plugins can work without  bogging down one's computer. 

May be I understand all that wrong, but that is what I think:
a) mastering plug-ins (with huge latency)
do not depend from / do not influence
b) hardware latency / buffer size
at least in theory (when (a) are written correctly)
 
Mastering plug-ins delay output by significant time, >>0.01sec. Free VST announced in another thread can show exact delay (Sonar does not expose that number, while it is aware about it). Such plug-ins are not "slow" because they need more CPU time, they just need more information "from the future" to make the decision. They can be CPU intensive or consume close to no CPU at all, as any other plug-ins. Some synths which are supposed to work life, can be rather CPU hungry. All plug-ins require some minimum system power to avoid glitches (which IS buffer size dependent), but absolute amount of that power is not plug-in type dependent. Important that after the level is reached, "normal" plug-ins produce 0 latency (the output buffer correspond to the current input buffer) while mastering plug-ins produce constant big latency (the output buffer correspond to the input buffer sent ~0.7 second ago for CW LP with default settings).
The conclusion from that part: with LP Comp. inserted, when you change something, you hear the result after 0.7 of a second. By "something" I mean not only life MIDI input but also volume changes, synth/FX parameter changes, etc. That is normal, by design, by definition of what these plug-ins do, nothing can be "fixed" nor speedup there.
 
About CPU consumption, the buffer size and mastering plug-ins. Some "simple" plug-ins which work just with one buffer theoretically can consume less CPU power when the buffer size is decreased, so if let say you have changed the size from 256 to 128, such plug-in takes 2 times less CPU power per buffer and so overall CPU consumption (per second) stay the same. In practice DAW/Hardware/Drivers add significant overhead and most plug-ins are not so simple, so we observe some CPU increase. Mastering plug-ins are working with more then one buffer per time, so when we decrees the buffer size from 256 to 128, the amount of audio information and so CPU such plug-in need stay the same. But it will be called 2 times more per second, so for mastering plug-ins 2 times more CPU consumption can be expected when reducing the buffer by half.
 
But please note that "big" buffer size you set in Sonar has nothing to do with the size such plug-ins need to process each time, for example 2048 buffer size for 44.1kHz is just 0,05 of a second while LP Comp pretend to use 0,7. Also the buffer "delay" should be added to the effect delay to get expected delay, in the example we can expect 0,75 sec.
 
With all that written, current version of CW LP plug-ins have a bug in the GUI design. Also that GUI can have some compatibility issues with graphic hardware, which can trigger audio clicks/glitches. That has nothing to do with your CPU power. And so, when reporting problems with new plug-ins, please check either these problems still exist when there GUI is closed.
 
I repeat, I do not pretend I am right with all that. That is my personal opinion only (but it is based on practical experience with VST/DX plug-ins development plus some signal processing background).

Well, that may not be a big deal, but I can use Ozone on either my Master Bus or on a mixed down audio track within the same project without changing any of my settings or setting up a new Mastering Project. Just saying...I would think that the "house" plug ins such as the new EQ and MBC would be so optimized as to not cause as many potential glitches as a third party plug in, which is written to be compatible with most DAW software out there. Maybe I'm thinking about this wrong, but as I stated before, I usually find CW add ins to be fairly smooth in actual use, although I might be forgetting the older plug ins where I stopped using them in favor of more robust newer stuff.
I am interested to see if this issue is less prevalent or resolved in a future release. For now, I can wait.

I can use a huge amount of FabFilter ProQ2s in linear phase mode. Even Ozone is mostly a heavy plugin because it does a lot of things at the same time. This has to be a bug or flaw in the code and I'm sure it will be fixed. 

Bob, that is my expectation, as mentioned in my most recent post. I certainly don't "need" to use this plug in at the moment, but I do like what I've learned about it, so hopefully there will be some greater stability and less issues in a future release.

I don't have the exact issue the OP has but I did insert the new Multiband compressor on a guitar track just yesterday and experienced some issues with bouncing.  When I tried to bounce the mix Sonar just stopped working.  I had to Cntl/Alt/Delete  and reboot to solve it.  I kinda thought it might be that plugin because I'd just put in in.  Sure enough after two unsuccessful tries at bouncing and then taking it out, everything worked.