Processor utilization issue

[dcompton]

I'm using Sonar 2.09 XL on:
Windows XP Pro
1.2Ghz Athlon
512MB ram
266FSB (ECS motherboard)
Maxtor 40GB (5400, I think)
Echo Darla
SoundBlaster Live Value
HP 8100 CDRW
Creative 52x CDR
Rage 128 Pro 32MB Ram

When I run Sonar 2.0 XL it seems to run as expected. Maybe a little slow if I have a few other apps open, so I try to avoid that. But the problem I see is that the XP task manager shows 100% CPU utilization, specifically during record and playback. I get this behavior even when it's just one audio track (usually guitar), with no effects. The Sonar CPU Usage meter show 1 - 2% utilization. I'm playing around with Cubase SX a bit, and I that app doesn't seem to produce this. I'm guessing maybe it's a configuration issue, but I'm not really sure. Plus I have no idea where to start looking. Any advice that anyone might have would be greatly appreciated.

Thanks!

[crosstudio]

no biggie, that's just the way Sonar works.

i found out a couple of months ago that it reserves the entire CPU and 'allows' other routines to have slices. i don't think its cakewalk's doing, i think it is directx.

[Major Tom]

Yeah, I discovered that behaviour quite a while back, (p4 1.6gig, Win Xp) I researched and found a couple posts where people reported the same thing. I don't know if its Cakewalk/Sonar or Direct x, but other programs such as a demo of ntrack studio, and other audio apps do NOT do this on my computer. Also, I have a version of Cakewalk Guitar tracks, it does the same thing....my bet is Cakewalk's audio "engine".

[Qwerty]

I think it has to do with the WDM drivers.

If I set mine to "Always USE MME" it seems to fluctuate more than the always 100% reading that the WDM give.....

No biggie - and I learnt and long time ago to use Sonar and not use anything else. YMMV.

Ciao,

Q.

[Major Tom]

On my system its not a WDM issue, since I have MME enabled. The Task Manager's CPU meter ALWAYS indicates 98-100% when playing or recording any audio or midi files, while Sonar's CPU meter indicates from 0-25% depending on the # of tracks, effects, etc. Your best bet I think, is to ignore it; it won't go away and it won't prevent you from making music, or for that matter running other apps while listening (not recording or mixing) to your creations, I do it all the time with no probs. My best guess is that somehow Cakewalk's audio "engine" either somehow reserves all of the CPU's cycles (but then, how could I run other apps while listening ?), or screws with the Windows CPU utilization tracking subroutines so that it reports full utilization in error. Or maybe the geek who wrote the code for Cakewalk wanted to play a little joke on us semi-computer-nerd-wannabes who would notice such a thing and be bothered by it ( I was !) and waste our brains trying to fix ( I did ! ) before they give up in frustration ( I have ! ) Be happy, don't worry, save your energy for your music...beat the geeks.

Hey, I am now a Senior Member, I must be right !

[dcompton]

I just wanted to say "THANKS!!", to those of you who responded. It is much appreciated.

MFM