Superior Drummer taking up cpu 40%! even cached! Am I doing something wrong?

[willl3]

any settings I'm missing

[bradch00]

What version of SD2 are you running? Is it updated to the latest version? What kit/preset are you using loading up? Any internal FXs in the SD2 mixer? Cached operations shouldn't really make a big difference CPU wise as it is designed to control memory (RAM) utilization rather than processor, if anything it may actually make it worse as every 'new' sample set that is required to satisfy a trigger needs to be then loaded into RAM.

Is your signature current? "Xeon Dual-Core 5150 2.66GHz"

[willl3]

What version of SD2 are you running?
the latest
What kit/preset are you using loading up
default


"Xeon Dual-Core 5150 2.66GH
i can't change the signature but using hpz820

[bradch00]

Looking for the version number top right right beside where it says "Superior Drummer".

Looking for the actual drum kit as my default is probably different than yours.

SD2 shouldn't chew up 40% CPU. What meter are you looking at that gives you the 40% CPU reading?

[willl3]

I just bought superior dummer ver 2.4.4
using ny avatar stock kit
my cpu is up 20 69%!!!!
i turn it off and I'm at 3 I'm using a z820 with xeon cpu.

I'm doing something wrong
H/W is at 256 samples
if I drop down to 1024 is only drops to 60...

[Darryl Ramm]

You talking 40% of the whole system or of one core? Reported by what?

You turn what off and you are at 3 what? You disable The single SD plugin and CPU (measured where? Total? Per core?) falls to 3% You have to explain yourself so others can follow. How exactly are you turning any plugin "off"?

System fully optimized? What troubleshooting have you done?

You just have a dual core Xeon. A hp z820 with dual-core 5150 Xeon?? Just do what is expected and post a Sandra report. Multiple posts dribbling out information, and it is still not clear what CPU you computer has.

So (unlikely,.... but) if a dual-core non-hyper thread in Xeon 5150... meh likely seen by many (including me) as pretty bottom of the line usable performance. Time to upgrade that.

And we cannot guess what sample rate or how many instances or what other plugins you might have instantiated, or just installed all of which are first things to need to understand.

Other standard/basic stuff (much under the "help us help you" link up the top of each DUC web page)...

Turn off dynamic plugin processing.

Make sure "ignore errors" is not checked.

Trash prefs (and do do as you try other things).

Make sure no plugins with known denormalization problems are instantiated (Sansamp, dverb, etc).

Try from an new empty session

Pull all other plugins out of the plugin folder and restart Pro Tools.

Create a new admin account and try from there....

[willl3]

I deleting prefs

60% percent of my cpu (indicated in system usage) gets used up if I just turn on the plug in
if the plug in is off it goes to 3%
I only have one track on
using default drum set with multi channel out.

using avid certified 820 hp
2 x xeon cpu e5 2640 2.5 ghz 22.gigs of ram

64bit win10.

makes no sense

[Darryl Ramm]

Thanks for the additional info. I'm lost have never seen this type of behavior. At this point I would still make sure you this this is not tied to an individual corrupt session (start with a new empty session not a template or copy in case it is corrupt) or user account. Once you check that then peel the onion... try uninstalling and reinstall SD, try reinstalling Pro Tools and SD, try a full clean Windows install... Somewhere along the way I would contact Toontrack support.

[bradch00]

What kind of performance are you seeing from other VIs? As Daryll asked, is this happening in one session? Have you created a new session and experience the same behaviour? This is definitely not normal. Worth a post in the Superior/DAW section of the Toontrack forum.

[Marsdy]

What buffer setting in Pro Tools?

Are you streaming the samples from your system disk? Not a good idea. With most of these sample streaming engines, the faster the disk the lower the load on the CPU and the system disk is busy doing other stuff.