Strange CPU Usage Issue with Sonar 6???

[Nate74]

While playing a recent project with about 16 tracks in it (44.1/24bit), I noticed the CPU usage right around 35%, which I would expect given the pluggins I was using the the number of tracks. When I stopped the playback, the CPU usage jumped up to over 90% and if I waited long enough, it would actually freeze the system up and the metter showed 100% usage. A couple times, I had to reboot to get working again.

In experimenting with it though, I noticed that by merely clicking on a waveform right when I halted the playback, the CPU usage dropped back to 0% until I started the play back again.

I've never had a problem like this and couldn't even figure out how to search the forum on this one...

Any thoughts would be greatly appriciated.

Thanks in advance.

[Freudian Slip]

That's an odd one. I have noticed at times on s7m that the usage jumps a bit when stopping playback, but it has never caused me a freeze issue. You might try shutting off "continue effects after playback stops" or what ever they call it. If that solves your problem you might be looking at a plug-in problem.

Do you have a previously saved version of the project? If so see if it plays fine. If it does start checking the differences between the two version.

Wish I could be more help. Good luck.

F.S.

[Nate74]

F.S. Thanks. I took your suggestion and sure enough, but turning off the "tails" the issue seems to be gone... I now have to go through the half dozen or so pluggins and see which is the culprit... honestly didn't expect that to be the issue, but it sure seems to be.

If I could email you a beer, I would

[Freudian Slip]

Originally Posted by Nate74

F.S. Thanks. I took your suggestion and sure enough, but turning off the "tails" the issue seems to be gone... I now have to go through the half dozen or so pluggins and see which is the culprit... honestly didn't expect that to be the issue, but it sure seems to be.

If I could email you a beer, I would

Cool I'm a bit suprised as well

F.S.

[Nate74]

Just as a follow up in case someone finds this thread in the archives someday... I never was able to determine which if any of my pluggins was causing the issue described above.

I tried removing each pluggin one by one, then replacing it as I removed the next one... nothing. I tried removing all usages of each individual pluggin one by one but nothing. There was a slight deduction in CPU usage each time I removed something as you would expect, but the usage was still higher after stopping playback than it was durring playback, until you clicked something on-screen.

Very odd indeed and I sort of miss the "tails."

[Freudian Slip]

Strange? Did you have the tails on while performing the tests to see which plug it was?

F.S.

[Nate74]

Yep, the tails were on, but no one pluggin seemed to be the culprit. I tried removing individual instances of each pluggin and tried removing them as like-groups, with the same outcome...

[Freudian Slip]

Pretty odd. I've got nothing more for ya. I run plenty of effects with tails on, and I might be running at 45 or 50% usage all the time without having your issues. My usage does jump when hitting stop, but not to the point of freezing.

Good Luck.


F.S.

[Nate74]

FS, now that's interesting to note; that your usage jumps up when hitting stop as well. If you click on something in the waveform view, does the cpu usage then drop back to zero? Almost sounds like some sort of glitch in the programming. Oh well, I can mix with no tails and maybe the next Sonar product I upgrade to won't do this... of course I was using Cakewalk HS2.0 for about 4 years so Sonar6 may be around a while

[Freudian Slip]

Well, I am using sonar 7PE. I am in the middle of moving my studio right now, but I belive it jumps and then lowers on it's own. It will be a while before I can look. Maybe someone else can shed some light.


Good Luck.

F.S.

[keith turner]

I have experienced the same cpu spike in Sonar 6.
I had previously chalked it up to my old Sonar 2 projects:
with Alien Connections Revalver DXi from Sonar1XL being the culprit.
Turn off Revalver spikes would go away.
Still not used to Sonar 6 and I am behind on upgrades again.

[Nate74]

I looked through the cakewalk site a bit and found no mention of this issue. I could use some updates though...

[cmhansen]

I've had the same problems also. In fact, I have one project that I can't open any more because when I saved the project it was at 100% CPU usage. It never would open again. Even in safe mode it won't open. Now when ever I save a project, I always hit a track to get the meter to read 0%.

What is strange is, on other projects that I have, with almost identical tracks and plugins, I don't have the problem. It's rather frustrating.

[Nate74]

Originally Posted by cmhansen

I've had the same problems also. In fact, I have one project that I can't open any more because when I saved the project it was at 100% CPU usage. It never would open again. Even in safe mode it won't open. Now when ever I save a project, I always hit a track to get the meter to read 0%.

What is strange is, on other projects that I have, with almost identical tracks and plugins, I don't have the problem. It's rather frustrating.

Crap, I didn't want to hear that! I was hoping there would be a generally accepted fix out there...I'm wondering if CW knows about this, since it doesn't seem to be an isolated occurance to just me.

[cmhansen]

Well, I didn't mean to worry you. But like I said, since I click on another track before saving the project, the CPU goes to 0%, and I don't have the problem.

I did go by Cakewalk and did a search tonight. And to tell you the truth, I couldn't find exactly the same type of problem there that we're having. The closest thing I could find was this...

http://forum.cakewalk.com/tm.asp?m=2...55435;�

I know it refers to Sonar 3, but while looking through the search threads for CPU usage, it appeared that versions 3-6, all had the same kind of problem. And this seemed to be the fix for it. May have to actually post there to find a solution to the problem, or definitive answer.

Another thread here...

http://forum.cakewalk.com/tm.asp?m=5...Cusage&#574218

Don't know whether I'd attempt something like this until I knew for sure it would work. Messing around with the registry and the keys is not something I feel comfortable with.

[Cudmasters Los]

You can go into the registry and find out what programs are running, and delete them from startup, frees up memory space.

click the start button, click RUN and type in regedit. I wrote that just in case you didn't know, not being smart, sounds like you do.

Below works the same in HKEY LOCAL MACHINE,AND USER


Software/Microsoft/Windows/Current Version/Run.

Under HKEY USERS, Click Default and then the above.

If you don't know what something is, google it.

By removing these startup processes, does not remove the programs from your computer. they will now only start up when you open them up on desktop...etc.

[yaknski]

Originally Posted by Nate74

While playing a recent project with about 16 tracks in it (44.1/24bit), I noticed the CPU usage right around 35%, which I would expect given the pluggins I was using the the number of tracks. When I stopped the playback, the CPU usage jumped up to over 90% and if I waited long enough, it would actually freeze the system up and the metter showed 100% usage. A couple times, I had to reboot to get working again.

In experimenting with it though, I noticed that by merely clicking on a waveform right when I halted the playback, the CPU usage dropped back to 0% until I started the play back again.

I've never had a problem like this and couldn't even figure out how to search the forum on this one...

Any thoughts would be greatly appriciated.

Thanks in advance.

Do you have a UAD-1 card installed in your rig by chance? That has been an issue for Sonar/UAD-1 users - CPU erratic behavior.