Sonar x3: Why did my performance drop massively after first run?

Do you have the file settings at 32 bit or 24 in preferences > File > Audio Data.

What effects have you added to the project? Some effects are CPU-intensive and only a few of these can be noticeable. If you hit "E" (to bypass plugins) does the CPU load alter drastically?

Hi Guys, I just received these answers now.

mettelus
What effects have you added to the project? Some effects are CPU-intensive and only a few of these can be noticeable. If you hit "E" (to bypass plugins) does the CPU load alter drastically?

Yes it does massively improve things. But as mentioned in the first run I was running WAY more of them (the really intensive ones). - And in 192 not 96.
I don't see what could have changed between now and then.
 

gswitz
Your problem is likely to be either IO or DPC Latency caused by one driver or another. I've had trouble in the past with a very stable system because I introduced a new mouse. LatencyMon can point you towards the problematic device.

Thanks, I will have a good look at both of those now.

1) Core 0 is the work horse for Windows. This is a simple fact you can never win.
2) SONAR is a host program, so CPU/RAM usage reflects your system, not SONAR.
3) Some plugins are scripted to do their grunt work on Core 0 as well... Another battle you cannot win, but can be mitigated by judicious work flow.
4) Cakewalk partnered with Intel to pioneer many CPU optimizations, and X3 is very evenly loaded for threads it controls (SONAR cannot override a plugin, only host it).
5) Many plugins are designed for use during mixing, so running low latency, i.e. "tracking" mode, with them can spike CPU loading immediately.

I am typing this on my cell since the forum is not working properly on any browser. You are using a nicety that SONAR provides users and assuming SONAR is the only contributor. It most certainly is not, and even the fastest machines can be brought to their knees with improper plugin usage and work flows.

Work flow and plugin usage is a better focus for "resolution." Even with high CPU usage, that meter is immaterial as long as you are not experiencing crackles or dropouts during play.
 
Edit: Could log in on the computer after posting... if hitting "E" to bypass plugins shows a drastic change, optimizing latency for "mixing mode" would be advisable (bump up the ASIO buffer to 128, 256, 512, or higher in Preferences->Audio->Driver Settings->ASIO Panel...). If more tracking work is required while mixing, bypassing plugins with "E" is the quickest way to mitigate dropping the ASIO buffer to a better tracking setting (without the CPU hit).
 

Also, have you tried bumping up your buffers to the max for your interface? This can impact cpu usage.

I tried re-installing it and this time the performance was exactly the same (poor).
I have no idea what's going on now...
 
 

I wouldn't reinstall myself. I'd try to sort out why you are red. Is it a laptop? If you have a Wi-Fi card disable it. If your computer has a battery, try disabling that too... plug in first. You should be able to enable again once you run down the source of the trouble. Basically we're trying to tune up your pc for real time audio. Once you are green, troubleshooting problems with performance should get easier. Btw you can sort the drivers tab by latency length, and that can help you figure out the problem. Once you get your pc dialed in, only hardware changes should require you to re check it.

There are some common tips like using high power settings so your USB devices don't go to sleep to save power. Checking to see if the pc can shutdown USB devices can sometimes cause dropouts.

Lastly, this type of thread is really common for new users. There are lots of forum members who can help you, but it is Christmas and few are paying attention right now. Be patient and persistent and you'll be rocking in no time.

Maybe the difference is pic cache ...

I may be confused here. The post with pictures of CPU usage with effects off and effects on shows the CPU loading of effects used. Which effects are you using in this project, and how many instances?

It is likely that a Windows process was NOT running the first time and IS running on successive attempts. 
For Sonar itself, investigate thread optimization and also core parking. Does not look like this is the issue but check it out. ( Just saw you had AMD CPUs, not sure these park cores or what Sonar Thread opt will do for these. )
 
For windows, disable Windows Update (set it to manual) , disable SuperFetch completely.
Double check that your HDD drive is using DMA mode and NOT PIO mode.
If running anti-virus, set it to not scan WAV files on the fly. I would simply disable A/V during sessions.
Try running Latency Mon with the Processes button pressed rather than drivers.
You will prob find some housekeeping chore Windows is doing.    

Also check out this tip (Week 35) from the Tip of the Week thread. For some systems it makes a major improvement, others not so much but there's no downside to trying it. I would highly recommend trying it if you're using an ATI graphics card and drivers.