What's the fix for ultra slow bounce--?

I'm sure I saw a post or thread about the problem with super slow bounces in X1 - and there was a fix?  But what was it?  I have the X1a patch, but bounce is still slower than grass growing.

?

Randy B.

John


I thought it was the a patch.

Thanks for the reply, John - Right, that's all I could remember also, that it was supposed to have been covered in the patch.  But this morning I did a test with one MIDI track of a monophonic line, just three measures - a few seconds of music.  Fast bounce took at least a minute. -- ! -- ?

Randy B.

emwhy


You can adjust the BounceBufSizeMsec in the Configuration file. Click on "EDIT" the select "Preferences", when the window pops up select "Advanced" at the bottom. You should then see "Configuration File" listed on the left column. The default setting on my system was 100, and that worked fine for bouncing and freezing, but some systems have a lower default value that slows down the process.

Ah yes of course, - I haven't thought about the BounceBuf Configuration setting in so long, I'd forgotten about it. 

I pushed "P" to get to my Preferences (good short cut if you didn't know about it, emwhy) and found that my BounceBuf default was set to 5 - ! - Good heavens.  Changed that to 100 and all is well now.  The same short little clip I tested with earlier took a reasonable amount of time to bounce this time - just a few seconds.

Thank you!

Randy B.

rbowser

John


I thought it was the a patch.

Thanks for the reply, John - Right, that's all I could remember also, that it was supposed to have been covered in the patch.  But this morning I did a test with one MIDI track of a monophonic line, just three measures - a few seconds of music.  Fast bounce took at least a minute. -- ! -- ?

Randy B.

Nice, It seems like just 2 weeks ago a Cakewalk representative was ridiculing a competitor for the fact that real time bounce takes longer than necessary.

Smoke? Mirrors? Spin?

Might have been worth reading the rest of the thread there.

Mine is set to zero. Should I change it?


You can adjust the BounceBufSizeMsec in the Configuration file. Click on "EDIT" the select "Preferences", when the window pops up select "Advanced" at the bottom. You should then see "Configuration File" listed on the left column. The default setting on my system was 100, and that worked fine for bouncing and freezing, but some systems have a lower default value that slows down the process.

jimmyrage

Mine is set to zero. Should I change it?

Zero is the default, and means that SONAR will use your real-time audio buffer size for bouncing. This can be problematic for some synths at small buffer sizes of 128 samples or less, and even at higher settings, it may not result in slow rendering.


Increasing it allows SONAR to process audio in larger chunks when rendering offline. Settings from 20 to 200 are recommended. The higher you set it, the more RAM is used during the bounce, and at some point you could conceivably get memory errors when bouncing, but that's unlikely at settings under 200.

 

About the higher setting modifying bounced 32 bit synths:  Can you clarify this? It seems important, and I have never heard of it.  Is this for all 32 bit synths that are bridged?  Is it only with bitbridge? 

Yea, I use the Korg Legacy synths (M1 and Wavestation) and I haven't noticed any latency issues with them as yet.
 
PS: My file is set to "0".  Should I just leave it there?

About the higher setting modifying bounced 32 bit synths:  Can you clarify this? It seems important, and I have never heard of it.  Is this for all 32 bit synths that are bridged?  Is it only with bitbridge? 

I don't think it is all Btibridged synths, but it seems to be a Bitbridge problem. Basically when you bounce some bridged synths (in my case it was BFD ECO), SONAR adds an empty buffer of silence to the front of the clip, effectively shifting the audio late by one buffer. The larger your buffer setting (or BounceBuffSizemsec, if not zero), the worse the timing offset.


I found that loading BFD ECO with Jbridge eliminated the problem, so I attribute it to a problem with Bitbridge. IIRC, I tested some other 32-bit synths, and didn't see the problem, so it may be an interoperability problem only with certain VSTis.

EDIT: BTW, I discovered this problem in 8,5, so it's not an X1 issue.

mike_mccue


Nice, It seems like just 2 weeks ago a Cakewalk representative was ridiculing a competitor for the fact that real time bounce takes longer than necessary.

Smoke? Mirrors? Spin?

I don't recall anyone ridiculing anyone. Fast bounce seems to work the same in SONAR as it always has AFAICT. No smoke, no mirrors, nor any spin.

I've been sitting here trying everything I can think of to get it to fail or take a long time etc and nothing seems to make it slower than normal. I've tried it with Cakewalk synths, NI stuff, UAD plugs, Rob Papen stuff, G-Media synths, etc so it's not inherently broken and being deflected.

I don't think it is all Btibridged synths, but it seems to be a Bitbridge problem. Basically when you bounce some bridged synths (in my case it was BFD ECO), SONAR adds an empty buffer of silence to the front of the clip, effectively shifting the audio late by one buffer. The larger your buffer setting (or BounceBuffSizemsec, if not zero), the worse the timing offset.

This is the info I was hoping for as I am a JBridge guy now.  I'll do a little testing myself.  Thanks for the info.

The buffer adjustment only helps slightly for me. The real fix is this: close the control bar before you freeze (hit "C"). Seriously. The difference while freezing a synth track is minutes versus seconds for me. This has to be (another) bug.

Yes, I've encountered this bug as well.  When the control bar is open, audio exports are painfully slow, far slower than realtime. When I close the control bar before export, the export goes lickety-split.

Incidentally, I have my bounce buf ms set to 50. I did some experimentation a while back and found that anything higher than that really didn't improve the speed.  YMMV.

amdrecording


I'm having the issue as well, and closing the Control Bar is the fix that works for me. In fact, I've noticed that my system is a bit more stable in general when that danged thing is not there. Hopefully will be a simple fix for the bakers!

-Alex

Has this issue been reported?  I see this message is from January, but the Control Bar bug still hasn't been fixed in X1B.  Really glad I found this thread, though; it was driving me crazy!

alexniedt



Has this issue been reported?  I see this message is from January, but the Control Bar bug still hasn't been fixed in X1B.  Really glad I found this thread, though; it was driving me crazy!

Isn't that amazing?  X1 - supposedly "the most popular version of Cakewalk ever produced" - but you have impossibly slow bounces unless you know the trick of closing the main tool bar, which of course isn't exactly intuitive, and is only an absurd work-around for a programming bug.  -- Wouldn't you think thousands of users all over the world have to be sitting there wondering "What the...?!"  - Well, they probably are.  And yet, it's "the most popular blah dee blah."  Amazing.

Randy B.