The question may seem strange, but each time I export a mp3 or a wave file, I monitor my cpu usage and it never exceed 30% ever.
 
I wonder if this is normal, if something is bottlenecking the cpu or if there's something wrong.
 
If the cpu could run at 100% I guess it would take way less time to render/export files...
 
The cpu is an FX-8530 with no heat issue (40°c max with 100% useage) and the receiving drive is a Samsung 850 Pro.
 
Any idea? Is it normal?

Not sure what your issue is here.  Fast rendering can create errors. Rendering to an mp3 will take longer.

SONAR has always been like this. The only programs I have which use full CPU potential are video rendering and encryption software.

Dyonight
 
 
If the cpu could run at 100% I guess it would take way less time to render/export files...
 
The cpu is an FX-8530 with no heat issue (40°c max with 100% useage) and the receiving drive is a Samsung 850 Pro.
 
Any idea? Is it normal?

Most systems start having dropouts or other difficulties when the CPU usage goes over 70-75%
So, you don't want it to go to 100%.

kitekrazy1
Not sure what your issue is here.  Fast rendering can create errors. Rendering to an mp3 will take longer.

Equally, with certain vsti's real time bouncing can also cause issues.
 
 

There are a few probable causes for bounces not using full cpu.
 
- Some plugin is throttling the processing speed. Even a single plugin can slow down the bounce since the rest of the system will wait for it.
- You are running at low latency. Increasing the buffer size can speed up bounces. There is in fact a config variable to set the bounce buffer size in Preferences | Audio | Configuration File, called BounceBufSizeMsec that allows you to have a higher bounce buffer size.
- Bounce is gated by your hard disk speed. i.e processing can only proceed as fast as your hard disk can write the bounced data.
- If you have compression like MP3 that is applied at the final stage so only one core will handle the compression while others wait.

Or you have multi-core bounce disabled...

But to reiterate you want some CPU overhead available while rendering to avoid audio glitches.

Ok thanks all!
 
I will precise that I'm speaking of offline rendering, so I'm not sure if the cpu overhead apply since there's no real time processing happening.
 
Great! So I'll increase the buffer size, be sure multi-core bounce is enable and see if it help.
 
I may use plugins that bottleneck the processing will have to check this.
 
And now I understand why mp3 take so long. If the lame encoder is not multi-thread enabled then my cpu is not exactly a single thread processing monster like a 4790k and look like it's the real limiting factor here.
 
Using an encoder that support multi-thread could really speed the mp3 export process. Is there anything I could use in Sonar instead of the Lame one that use multi-core?
 
That's not a real problem but that would be nice.
 
Thanks!

Noel Borthwick [Cakewalk]
 
- You are running at low latency. Increasing the buffer size can speed up bounces. There is in fact a config variable to set the bounce buffer size in Preferences | Audio | Configuration File, called BounceBufSizeMsec that allows you to have a higher bounce buffer size.
 

Nice!
 
Any number would be recommended? Should I increase it in 64/128 steps? (It's a sample value in binary number right?)
 
Thanks!