X3 CPU load??

A simple two-track audio recording that runs seamlessly in X2 with lots of Pro Channel toys stutters horribly in X3b when running flat.  Does X3 intrinsically make greater demands on a system?  Doing what?  Admittedly I am running a marginal old system - AMD Athlon II 64 2.8 GHz under Win 7 with 10GB Ram - but, I can A-B between the 2 programmes, X2 is smooth, X3 unusable.  What have I missed?  Optimisation suggestions would be much appreciated!

I have an old PC (phenom2 X4) and do not have any problems...Sounds like a driver setting  issue in X3. Make it the same in X2 and X3..

Thanks for all your assistance, guys.  Luckily I had my SWA Complete Sonar X2 Overview to hand to help with the wrinkles of this process!

dlesaux

stevec
Q9300 w/ GB RAM here, and X3 is as good as if not slightly better than X2 overall.   You may want to try renaming your aud.ini file and let SONAR create a new one.

This caught my attention! What's the rationale for doing this? I too have noticed a slightly higher load on CPU usage since I moved to X3. Where is the audi.ini file? Why does this help with CPU usage?  Just trying to understand..

it resets all driver settings.
copy the file to make a back up
(always good t make a back up incase you don't like the changes and want to get back to what you had)
 
then restart sonar and x3 will rebuild a new aud ini file

^^^^^^^^
 

I´m having the same issue, X3 is a about 20% more cpu hungry than X2.
 
Just tested with the same Project on both...
 
In projects that before I was on the limit (60% cpu usage) ...on X3 now they are about 75% and I start to hear "clicks and pops". This is with the same buffer size and latency. On another project ..X2 was 18% CPU and X3 25% CPU.
This is in a quad core I7 920
 
Anyone solved it deleting the AUD.INI file??
 
Daniel

I would recommend renaming instead of deleting in the event that it doesn't help - that way you have your original settings still intact.   For that matter, even if it does help, you can still compare the old and new settings to see what's changed. 

Thanks for the tip. I wasn't having any problems but I want to have the best settings possible for X3. I followed the above instructions. The aud.ini file went from 6kb to 3kb. 

scook
The need to rename the AUD.ini does not happen that often. 

Yep. If you consider the renaming will force X3 to rebuild audio settings, there's no point in doing it multiple times, unless you are changing your hardware or there's an X3 update. If that's not the case, you'll just create the same aud.ini over and over and won't get any benefit.
 
The initial renaming is done only to ensure there's no X2 configuration infos anymore. So, if you get problems after a aud.ini rebuild, you should try to tweak settings instead of expecting a rebuild to correct them.
 
People should not forget too that sonar may not be the problem. Vsts are plugins which are eating power and may be buggy in certain conditions (especially when using bitbridge) . You can't just stack 10 of them on each one of your 40 tracks and expect that you'll get your 400 plugins running with latency compensated  and consuming only 10% of your main cpu core. Freezing tracks is there for that reason.