1/2 my life passes watching that thing crawl across the screen. And oh what a bummer when I'm mixing a 3 hour recording and I forget to highlight the range of the tune I'm bouncing! Gives me plenty of time to post... haha

If mix down/bouncing seems to take longer than it should try increasing BounceBufSizeMsec in your ini file to something like 100. That is a documented fix CW Knowledge base article

FastBikerBoy


If mix down/bouncing seems to take longer than it should try increasing BounceBufSizeMsec in your ini file to something like 100. That is a documented fix CW Knowledge base article

This, of course, begs the question - why the heck don't they increase the default value of this out of the box?
 
Also, as I've mentioned before, if you have any audio snap in your project, all the work is going to happen on a single thread, which slows things down unbelievably.  According to Noel, this is on the to-do list to fix.

gswitz


1/2 my life passes watching that thing crawl across the screen. And oh what a bummer when I'm mixing a 3 hour recording and I forget to highlight the range of the tune I'm bouncing! Gives me plenty of time to post... haha

You do know that you can abort whatever operation you're carrying out at any time by clicking on the little 'X'


Sonar will ask you if you want to keep the partially rendered audio - I've never seen the point of the 'Yes' option

Silicon Audio

FastBikerBoy


If mix down/bouncing seems to take longer than it should try increasing BounceBufSizeMsec in your ini file to something like 100. That is a documented fix CW Knowledge base article

This, of course, begs the question - why the heck don't they increase the default value of this out of the box?
 

I guess because not everyone needs to change it. A setting of zero will use the mixing latency set on your audio interface which for may or may not work well on a users setup. If it is working okay there's no need to change it.

I'm a little confused after reading the Support knowledge page, but I'm a bear of very little brain, so no surprise there..
 
I've noticed recently that when I export audio with fast bounce enabled the timing of some of the MIDI instruments is all over the place.  This never used to happen. I now have to bounce in real time to remedy this.
 
After reading the second paragraph on the support page I looked in the config file and my BounceBuffSizeMsec was set to 100.  I changed this to 0, and performed a export with fast Bounce enabled.  It did take longer than before, but everything sounds in time.  And it was still quicker than a real Time Bounce.

Back in 1996 I remember My 486 would take 40 minutes just to normalize a stereo wave file . Very discouraging... The Galactic Fedaration has computers that blow ours away ..... It won't be long and we'll have ours too.

@bristol_jonesy I know you can cancel the bounce, but it takes a while to even cancel - measured in minutes for me if I select all (often 8 or more 24 bit aud trax) and normalize (key strokes I hit very fast). Usually I just normalize the range of a particular tune I'm bouncing, but if I don't click the ruler bar between the markers first, it will hang a while. No big thing, but that's what I was talking about.

Really, I find that what I use depends on the speed. When I get more speed, I just use it with more plugins. I find I'm willing to spend two or three hours on each song. How much work I do is limited by the time I'll spend, and the faster Sonar and my PC are means more time for automating envelopes and auditioning plugins and stuff like that.

That doesn't sound right - it takes literally a few seconds here.

But then again, we don't know anything about your system.

List your FULL system specs in your signature

@Bristol_Jonesey
Your confidence was so great I just tried it to make sure I wasn't mistaken.

The project has 11 24 bit tracks and is 2 hours and 55 minutes long (a little more). I selected all tracks. Alt>P>N to normalize and hit OK. It wouldn't do anything if it worked anyway since there are normalized moments in all tracks. Then I hit escape.

The screen went ghost ish (I could see but couldn't click and everything is a lighter color) for 6.5 minutes

I use Windows 8 x64 and Sonar Prod X2 X64 but this was true on my system for X1 and Windows 7 as well.

I use a fast track ultra interface (m-audio) in asio mode.

When the Escape hitting finally took effect, I got this message...

The error reads File write failed... path... edit(25).wav.
 
Component Details Subscore Base score
Processor Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz 6.4 3.3
  Determined by lowest subscore
 
Memory (RAM) 4.00 GB 6.4
Graphics NVIDIA GeForce 9200M GS 3.3
Gaming graphics 2031 MB Total available graphics memory 5.0
Primary hard disk 34GB Free (149GB Total) 5.2
Windows 8 Enterprise