Zo

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 ...

Zo,
Are you saying you have 30 instances going of the tape sim?
 
Brian

Just as a thought, did you compare Sonar to Reaper using VST3 plugs in both programs? I didn't think Reaper supported VST3 or is that a recent thing? Just saying, there could be a performance difference between VST2 and 3 since the latter is a way more extended protocol.

30 instances of the J37 is bound to suck some CPU. I assume by your HP model, you're on a laptop with a Single-Core -i5 processor?
 
Laptops in general typically are under-clocked CPU's to lower heat, offer slower buss controllers (not to be confused with Mixing Busses), and if you don't have enough RAM onboard, you will take a serious I/O hit for swap-file usage. Not saying this is your problem, though.
 
You're also not running the 32-bit J37 in 64-Bit Sonar, correct? Try the VST3 version of the J37 as well as the VST2. See if that makes a difference.

<p>

brconflict</p> <p>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!</p> <p>&nbsp;</p> <p><br />

 
may i ask you a screen shot of the cPU hit of 30 (stereo) instances of J37 my friend please ..

You have an active thread on this subject running on Gearslutz. Why not keep it running over there.

Zo

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 ...

Zo, You're previous posted specs indicate that all your PC OS's are 32 bit.
Maybe you're maxing out your resources...

I currently have a session of 22 tracks, and maybe 2-3 Waves plug-ins per track. I can watch my CPU (4-Core, 8-threads), a 64-Bit Intel 3.5Ghz Proc begin to spike pretty heavily as I add some Waves plugins to each track. For example, Waves NLS on every track will double CPU utilization in my case. Many projects I work on require me to freeze tracks often. Modeling or Convolution plug-ins are heavy on CPU, despite what Waves fans will tell, you, but as the CPU power increases over the next few years, we'll see this becoming less and less of an issue.

Zo
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

If you want to pass a project along, I can surely dive head first into this on our machine here at HQ to check out any specifics. I have VTM here as well. PM me and we can set that up.
-DG

In my particular case, the addition of a SINGLE instance of a Waves VST in X3b caused 
the CPU to Spike, and it would not go back down, even after removing EVERY other
plugin in the project.  I'd say that's an issue...also, I inserted ONE instance of the
Softube FET Compressor VST 3 in a very small project (5 tracks) and X3b crashed.
I'm guessing these issues are VST 3 related.

Haven't checked it in 3c yet...

There are also some pretty big Graphics issues with Faders/Knobs jumping and erratic...
and this problem still persists in X3c, as I posted earlier.  

I'm pretty sure the fader/knob issue is somehow related to Touch, but can't swear to it.

My specs are in my sig. and EVERY OTHER program I use, including 6 other DAW's are perfectly
fine with mouse handling, they are all smooth as silk...only X3 has the problem, so I'd say that says
a lot towards trying to point the finger elsewhere (not that it's not possible).

My mouse is a Microsoft Bluetooth Mouse 5000 - and, for what it's worth, I shouldn't have to jump
through 50 hoops for it to be ok with X3 when it's fine everywhere else...without doing anything,
but that's just my opinion.