ok guyz have a look here :
 
http://www.gearslutz.com/board/new-product-alert/876717-waves-abbey-road-studios-present-j37-tape-saturation-plugin-4.html#post9511363
 
the thing is simple ....waves plugins (some of them) are ultra light on some daw and cpu hogg in sonar , witch make them unsuable ...
 
Bakers , are you in touch with Waves iiin any way to check this out (to see at least if it's waves or sonar or both)
 
even my VTM cpu hog is less consumming than waves MPX ....i don't even talk about the last Waves J37

I've been using multiple instances of Waves Kramer Master Tape, NLS, Helios, and PAZ Analyzer with X3 Producer with no problems on an older Q9550 2.83GHz Core 2 Quad machine. Is it possible that something else is going on Zo? I don't know a bunch about computers, so that's why I'm asking.

no issues in particluar just more cpu hungry than in reaper or some other daws .....so i think some isn't playing good ...

Sonar X1 and X2 is supported by Waves - but not X3, yet or not at all, I don't know.
 
So Cake has probably been in contact with Waves for X1 and X2 at least.
 
Your description is really vague - and no computer specs or anything.
I think a specific project setup would help to compare - and give Cake a chance to look at it.
 
I have not fiddled with X3 settings so much yet, but in 8.5 I added some stuff when I got my i7 machine to run more smooth. It was settings in AUD.INI as I remember.
 
I also changed many BIOS settings in computer to allow all cores running all the time, not allow dynamic overclocking etc. Different software is a different builld and will be affected more or less with these settings and most likely are having different default settings.
 
I know Reaper is very low on resources but there are big differences between plugins as well. The Marroquin bundle is really high on any daw.
 
And Reaper is using a different graphics library it seems - some plugins like Dorroughs meters does not even draw on screen to be usable at all in Reaper.
 
And finally - don't rely on cpu meters in either daw - look at system level what is used. How you do it on the daw may differ a lot.

sonar X1
32bit test done on my HP 8560W I2670QM Quadro FX 1000M
RME UCX
tried waves with and without X ray exclusion ....just saying ....
 
System OK
Soundcard OK
project OK
 
Reference Slate VTM (witch is know to be cpu hungry) ....less hungry than waves MPX 

All waves plugs working as expected in X3b here!

X3b is supported by Waves. Waves also has a new sub-release (r14) that was just recently posted (this week?), that  includes the new J37 Tape Sim, which I purchased. If you're having issues with Waves, my suggestion is to only install the 64-Bit versions (you have to put the 32-bit versions in a directory Sonar doesn't scan). Then have Sonar only load the VST3 versions of the Waves plug-ins.
 
With this in mind, I've only had only two X3b crashes with Waves plug-ins. I do use them pretty heavily on a 3.5Ghz 4-Core/8-thread Intel CPU. I highly recommend the 8-thread CPU, btw. Sonar sees this as eight separate CPU's.
 
If you're still experiencing high CPU utilization in Sonar, not only should Cakewalk be able to help, but so can Waves. They know Sonar pretty well.

There were some issues with Waves plugins and their GUI's in Sonar in X1/X2, but these issues appear to be fixed in X3b. I've never noticed them consuming more CPU than other plugs. 

Some do suck up some CPU, but for good reason. Such as the IR-1, for example, the convolution reverb is pretty heavy if used abundantly across tracks. The Waves Tape plug-ins can be heavy as well, but if you use it frequently, turn off the Monitoring button, and don't use flux, delay, wow and Flutter on every track. You don't need those unless you're specifically looking for character of that magnitude. There, I would only use the Tape Sims on busses, which is where I use them specifically, anyway. Hope this helps!
 

brconflict
Some do suck up some CPU, but for good reason. Such as the IR-1, for example, the convolution reverb is pretty heavy if used abundantly across tracks. The Waves Tape plug-ins can be heavy as well, but if you use it frequently, turn off the Monitoring button, and don't use flux, delay, wow and Flutter on every track. You don't need those unless you're specifically looking for character of that magnitude. There, I would only use the Tape Sims on busses, which is where I use them specifically, anyway. Hope this helps!
 

may i ask you a screen shot of the cPU hit of 30 instance of J37 my friend please ...