Hi Sonar users,
I'm running into a weird situation everytime I bounce audio (Using bounds to clips right click menu).

I recorded an audio piece & edited it & now I'm ready to create a loop. So far everything is works perfect. I bounce the audio. When I play back, the audio (not just this track, everything) is completely distorted. Softsynths are playing distorted & way off time. I have to restart sonar once this happens. Has anyone run into a similar situation?

Here is what I'm using:
896mk3, TI Chip firewire interface, Producer 8 on vista 32 (q6600, 4GB RAM). I'm using quiet a few softsynths & reason.

Any suggestions will greatly help. Thanks in advance.

Kal

You might need to increase your mixing latency. It could be as simple as that. You can also try a different drive mode to see which one might perform better at lower latencies.

Edit: well I meant driver mode

Thanks Richard. I tried right after posting (increased the ASIO buffer). It's playing fine now. But the latency is at 43ms. Should I be concerned?

A newer, really fast computer with a decent soundcard can run at 1.5ms latency, but that latency typically needs to be increased as a project grows depending not only on track count but the number and resources needed for effects and synths.

Hi , I got a similar situation.
 
Everything (audio and synths) plays fine until I do a bounce-to-clip.  After this all the synths start to sound distorded/fragmented.  The audio clips (not the synths) continue to play well (undistorted). 
The problem disappear if I (save the project) and I restart it, restarting the whole program Sonar X2 (but I had the problem also with Sonar X1).
 
I tried the suggestion I read in this forum, incresing the latency ... without restarting the program ... and effectively (if I increase it alot) the problem disappear.
 
Anyway it is not logic to solve such problem increasing the latency because, as said, it works fine (with the smallest latency)  until I don't do any "bounce to clip".
So it is the "bounce to clip" action that "brokes something".  
 
The problem should be solved by the developers I guess (I am a computer developer too) 
 
NOTE : effectively my project is a big project with many synths and a long track 18+ minutes

Could it simply be that the bouncing creates so much new audio, that the buffer become insufficient??
If you bounce without archiving the original tracks you get rapidly new load on CPU.
 
It does not matter how much latency you have when you're mixing. You need low latency only when tracking.

Is this happening only on fast bounces or real time as well?
 
What happens if you freeze the soft synth (not the track) rather than bouncing?

There is a separate bounce buffer, whose size is normally linked to the normal buffers, but can be separately configured for just this situation. It's called BounceBufSizeMsec. If it's non-zero try setting it to zero. If that doesn't do the trick, set it to the maximum of 350.
 
Another variable that might possibly apply is AllowOfflineRenderMixThreads. This just enables multi-threading when bouncing, normally a good thing, but can cause clicks in the audio under rare circumstances. It's worth a try to set it to 0 (disable) and see.

Kalle Rantaaho
Could it simply be that the bouncing creates so much new audio, that the buffer become insufficient??
If you bounce without archiving the original tracks you get rapidly new load on CPU.
 
It does not matter how much latency you have when you're mixing. You need low latency only when tracking.

No it isn't my case, it happens even if I do "bounce to clip" of very small clips

bitflipper
There is a separate bounce buffer, whose size is normally linked to the normal buffers, but can be separately configured for just this situation. It's called BounceBufSizeMsec. If it's non-zero try setting it to zero. If that doesn't do the trick, set it to the maximum of 350.
 
Another variable that might possibly apply is AllowOfflineRenderMixThreads. This just enables multi-threading when bouncing, normally a good thing, but can cause clicks in the audio under rare circumstances. It's worth a try to set it to 0 (disable) and see.

I tried to do such setup  (setting it to 0 and low values like 10) but the problem remain unchanged.    Ugly bug!