performance module..mine starts at 22% cpu's to begin a project.

trying to round up some figures here.when i open up a normal project in x1 my performance module reads 22%...this before i even lay a track down or put in a vst.wondering where this stands on your average

Yeah Charlie how are you checking that? I don't see any movement in Sonar but I don't know how to read the exact figure percentage.

by the way..im sorry i did nt say this...to check the disk space or cpu..hover the mouse over the bar..typicaly right at the left of the tip of the orange bar..

I am not sure I follow

@startup: I have no cpu usage unless I start to add fx, instruments, etc. Is that what you mean by 22%.......just starting it up?

@task manager/performance meters: Although some can give what is imho an elaborate answer (that most of us just don't understand) the task manager and the performance meters have NEVER been the same in any version of sonar I've used (8.5/x1 currently)

I think the X1 Performance module only shows the amount of CPU it's using. I don't think it shows the total system usage. I may be wrong on this.

Anyway, start Task Manager and check your % CPU usage before and after you start X1. And then load a project and keep watching it.

I just did this:

Running Win7 64-bit i7 920 w/12 gig ram at 96khz/24bit 64-bit double precision engine enabled:
 
 
Win7 only no other apps open                                                              CPU Usage = 0 - 1 % but then drops to 0%

X1a opened with no project                                                                  CPU Usage = 1 - 2 % but then drops to 0%

X1a opened with large complete song project song not playing           CPU Usage = 3 - 24 % but then drops to 0%

X1a opened with large complete song project with song playing         CPU Usage = 7 - 44 % and keeps bouncing up and down

X1a opened with large complete song project song stopped               CPU Usage = 3 - 22 % and keeps bouncing up and down

X1a opened after closing project                                                          CPU Usage = 3 - 14 % but then drops to 0%
 
Win7 after closing X1a                                                                          CPU Usage = spikes to 3 % but then drops to 0%
 
Hmmm...

This is my DAW only computer with no virus scan or internet or even any other apps, X1a only.
 
Hope this helps.
 
EDIT: Damn! I totally forgot to check the Performance module in X1a

Created New "Test Project"
Launched Blank Template-
Disk Load (0%)
Disk Space (11%)
System Memory Commit (2.0 Gb/12%)

14 Track/4Bus Template Fresh/No Recordings armed to record
20 various inserts/sends (Perfect Space/GR4/Reverb/Compressors, etc...)
All same except -
System Memory Commit goes up to 13%

200 Track/8Bus
Loads of FX/Tools loaded sitting at 17%/2.8 Gb

This is without X1 running (Play or Record) on my system

chuckebaby


sorry for the multi posts here..(post count matters..lol)..seriously,to be more specific..my task managers performance and sonarx1 permance "module" are not reading the same..trying to comfirm if this is normal,which i believe is not.

I think the different "readings" are routinely observed by anyone looking at both simultaneously. I don't think, the difference in readings, in itself, indicates a problem.

best regards,
mike

Oddmeister


I had a similar scenario where a blank project (no plug-ins or instruments loaded) was reporting a CPU load of approx 14%

I deleted the AUD ini and this cured the problem.

Hope this helps.

Oddmeister 

how do i delete the aud. in..and whats it for..is it supposed to be delted..i think i remember reading that somewhere.

chuckebaby


there is a lot of data in the aud.in file..like every single interface ive ever tried..a few i had borrowed to try out and deleted or uninstalled the drivers..there still in the aud in file.is it a good idea to maybe delete this and give it a shot..i mean it cant hurt right?

Make a backup of AUD.INI first, Charlie.   It's ok to delete it - Sonar will rebuild it, but you will have to check every option to see what changed.
 
One reason to delete aud.ini is in a drastic situation where something got messed up and your audio is not working right.
 
So make the backup, delete it (do it all while NOT running Sonar), relaunch Sonar.  Then check all your settings.
 
BTW, the Sonar meters are NOT the same as the Windows task manager meters.   The two report somewhat different values.
 
 

thank you guys..i really learned alot and truley am greatful for your help.

i did find it billy im getting ready to make a copy of it now..hopefully this will take care of some of the performance issues rising as of late..i never had a problem with sound till a few days ago..i did a project with a lot of vst's and a soft synth(strings)and that seem to break the back..after that my memory went up and sound quality is suffering..not really bad..but enough where there are a few pops and clicks in the mix,already reinstalled sound drivers didnt seem to work so heres to hoping this does..thanks

chuckebaby


thank you guys..i really learned alot and truley am greatful for your help.

> Im glad to see your working this out charlie . its quite
   a process with great rewards +8 !!

chuckebaby


ive got it down to 17% now,thats after deleting aud.in(no problems there)i also stoped some programs from running at start up which there are more i need to look into.and i changed back round services.sound quality is much better..i believe the project i was having issues with was currupt and no longer going to use it..many hours lost.but iguess thats the breaks

What is down to 17%? I suspect it's memory usage, not CPU. AFAICS, there's no way in X1 of determining a number for CPU usage. The bottom bar you refer to in an earlier post is "System Memory Commit" on my version of X1. Can you post a screenshot?

Cheers, Peter.

chuckebaby


ive got it down to 17% now,thats after deleting aud.in(no problems there)i also stoped some programs from running at start up which there are more i need to look into.and i changed back round services.sound quality is much better..i believe the project i was having issues with was currupt and no longer going to use it..many hours lost.but iguess thats the breaks

Charlie, if you're talking specifically about Sonar's CPU meter (as opposed to Task Manager), keep in mind the Sonar meter is measuring audio buffers not really the actual CPU demand.
 
So if you're seeing spikes, that could relate to anything audio related (audio driver, cables, latency settings, plugins pumping through the project, streaming data, etc).
 
So re-check all your audio related settings.
 
My "normal.cwt" in both 8.5.3 and X1 (though I'm not using it lately) hovers around 17% on 32bit system but I have a number of plugins (Maschine, a bunch of FX, etc) - so I find this normal on my system.
 
 

HumbleNoise

PeterMc

chuckebaby


ive got it down to 17% now,thats after deleting aud.in(no problems there)i also stoped some programs from running at start up which there are more i need to look into.and i changed back round services.sound quality is much better..i believe the project i was having issues with was currupt and no longer going to use it..many hours lost.but iguess thats the breaks

What is down to 17%? I suspect it's memory usage, not CPU. AFAICS, there's no way in X1 of determining a number for CPU usage. The bottom bar you refer to in an earlier post is "System Memory Commit" on my version of X1. Can you post a screenshot?

Cheers, Peter.

Yeah Charlie Peter's right. The CPU usage is the little bars on the far left, the bottom bar you are reading is NOT the CPU usage, it's memory commit as was mentioned above. Mine starts out at 1.9 gig (23%). When I start up a project the little CPU bars (4 in my case for the quad core) start jumping around but I can't tell how to measure them.

Sound like you got your project repaired so that's a good thing.

Yea, I kinda mentioned that way back in post #10.

Hey Larry,

do you mean "System Memory Commit:" ?.  When you hover the mouse on the lower orange bar ?.

The CPU usage shows as vertical bars on the left hand side in the performance module.

There's been mention in other threads about the lack of a "digital CPU readout" like there was in 8.5.
It would be nice to have for sure, but I haven't actually found it a big bother - the bars work for me.

But then again, I haven't had to look hard at CPU usage with my new box.

Reading through the thread it looks like a corrupt project caused the issues that sent Larry on the hunt for system problems. Not much fun, I've had X1 corrupt projects but never lost more than a couple of minutes work
because I'm always saving new versions.

Cheers - Cliff