Re:Export audio does not use CPU fully
November 12, 10 3:32 PM
(permalink)
It depends heavily on the nature of the project. A pure audio project with effects frozen will slam your hard drives, and hardly touch the CPU, while a pure soft-synth project with active effects should hit your CPUs pretty hard.
As a reference point, try loading up the Dark European Space Adventures demo and exporting that.
On my Q9550, it will average 75% on all cores, with Core1 running at 85%+. If I freeze all the tracks, my CPU averages less than 5%, and my disks run at 85%.
My guess is it's not possible to utilize 100% of the available CPU cycles on all cores, but 80-90% on the most heavily loaded core seems reasonable to me.
Regardless of what level your CPUs are running, you might be able to shorten the time it takes bounce/export/freeze by setting a higher value for BounceBufSizeMsec=0 in AUD.INI.
With the default setting of 0, SONAR uses your real-time buffer size for offline processing as well. Increasing this parameter let's SONAR process audio in larger "chunks" offline, which can be more efficient. Values up to 200 or so are reasonable. The higher you go, the more RAM is needed, and you can get in trouble going too high. I have mine at 20.