I think for a problem of this sort there'll be a fix out sooner than later. So there's a few options unless your livelihood depends on your using fast bounce at this very point in time.

Rollback and miss the other features, enhancements and fixes that came with Foxboro.
Stay with Foxboro and postpone your instant gratification for fast bounce.
If you absolutely have to bounce, there are other bounce options available, they just take more time.
Be reasonable.

mudgel
I think for a problem of this sort there'll be a fix out sooner than later. So there's a few options unless your livelihood depends on your using fast bounce at this very point in time.

Rollback and miss the other features, enhancements and fixes that came with Foxboro.
Stay with Foxboro and postpone your instant gratification for fast bounce.
If you absolutely have to bounce, there are other bounce options available, they just take more time.
Be reasonable.

Well... it's actually a quality/reliability issue. I used to always use real time bounces until I learned that "Fast Bounce" doesn't necessarily mean "Faster" or "Inferior to" Real Time.
 
Essentially if the project requires more processing power to export it will do so (and take longer/fluctuate export speed as needed) using Fast Bounce to acheive the best results whereas with Real Time it is stuck at a certain speed which could lead to dropouts and whatnot in teh final results.
 
Most of the time not an issue I guess but still... it's a real pain having to go back and re-export stuff. Now that I think back, since I switched to Fast Bounce I can't recall a single time when I had any audible export related issue. I do recall having them on occasion when I insisted on using real time because I thought it was superior.
 
As I said I'm sure it will be fixed promptly but this is kind of a biggie if it is indeed confirmed.

Pro Tools didn't fast bounce until about 2 weeks or so ago, didn't it?
Its the industry standard
Whats the big deal?
 
T

Hey folks, sorry about the bounce tempo change issue.
It was caused by a subtle change that happened earlier on in the cycle. The reason it wasn't noticed during testing is because the problem tends to be intermittent and it depends on what you played in the project or where you clicked on the timeline earlier. While debugging it it took forever for me to find a recipe that was deterministic.
 
Anyway the problem has been fixed. We will release it officially once it has been validated but that is likely to be early next week. In the interim you have two possibilities. You can roll back or use realtime bounce and it should work fine.
There is also a 3rd possibility <g> if you are brave and want to test this build here is a link where you can get the updated SONAR exe from here. Note that this is a "loose exe" so you will need to copy the proper flavor (x64/86 or Platinum/Pro/Artist) to your SONAR programs folder. If you test it let me know if it works.

Thank you , Noel.
 
 

Thank you , Noel.
 
/so thankful apparently it was worth looping... lol
 
 

Well the workaround is not to use fast bounce, some DAWs don't even have that facility ... I think my policy of waiting at least a few weeks before I update is working for me. Haven't installed it yet.

Beepster

mudgel
I think for a problem of this sort there'll be a fix out sooner than later. So there's a few options unless your livelihood depends on your using fast bounce at this very point in time.

Rollback and miss the other features, enhancements and fixes that came with Foxboro.
Stay with Foxboro and postpone your instant gratification for fast bounce.
If you absolutely have to bounce, there are other bounce options available, they just take more time.
Be reasonable.

Well... it's actually a quality/reliability issue. I used to always use real time bounces until I learned that "Fast Bounce" doesn't necessarily mean "Faster" or "Inferior to" Real Time.
 
Essentially if the project requires more processing power to export it will do so (and take longer/fluctuate export speed as needed) using Fast Bounce to acheive the best results whereas with Real Time it is stuck at a certain speed which could lead to dropouts and whatnot in teh final results.
 
Most of the time not an issue I guess but still... it's a real pain having to go back and re-export stuff. Now that I think back, since I switched to Fast Bounce I can't recall a single time when I had any audible export related issue. I do recall having them on occasion when I insisted on using real time because I thought it was superior.
 
As I said I'm sure it will be fixed promptly but this is kind of a biggie if it is indeed confirmed.

Well....no . It's a small coding error that's already been fixed. As Noël said roll back, try the Sonar alpha Exe or do real time bounce.

Doktor Avalanche

Sir William
I am a user from Pro Audio 9 but I am coming to the opinion that SPlat is becoming all fancy toys and less functional.

I think this poorly phrased. I would not put it like that.

However I would like to see a return to fixing and improving the meat and potatoes of Sonar (pre Platinum). If we look at the last few releases it's been more about fixing issues with the new Platinum features. I'm glad they are being fixed rather than not, don't get me wrong but I want existing functionality improved. I hope there will be less new headline features, and more exisiting workflow tweaks and fixes from next month. More streak and potatoes and less cucumber please.. Core program still needs improvement.

+1 - completely agree.

My point was it's a pretty big deal to have a commonly used and crucial feature such as Fast Bounce go wonky which is why it likely got such immediate attention. I'm not freaking out... just sayin'.
 
If anything the speed at which this got pounced on is a pretty good sign for the future of the program.