I love the workflow of speed comping, but I have a recurrent problem that limits its usefulness.
 
At first, when I start the process of auditioning clips in takes (using SHIFT+SPACEBAR and the arrow keys to navigate), everything goes fine. But inevitably, after a while, I start getting noise when I jump from one clip to another. This gets worse for a while, and then I always get a dropout. I can start again with SHIFT+SPACEBAR, but pretty soon I get a dropout every time I change audition clips.
 
I have tried increasing my ASIO buffers to 1024 samples or higher, which seems to have no effect. I've also tried increasing my playback and record buffers in Preferences, and this seems to help a little, but not enough.
 
Has anyone else had this? 
 
 

Might be worth trying to reduce the I/O record/playback buffers as well. Buffers taking too long to fill will also cause problems.
 
There's usually a balance to be struck between ASIO buffers and I/O buffers. You are definitely on the right track though. Increasing ASIO buffers should help, not sure why they aren't. Are you running a lot of processor hungry FX? Try switching those off (Press "E" to bypass all). That should also help.

I was going say increase buffers. It sounds like a traditional dropout to me. This means your Pc can't feed the audio data to sonar fast enough or your pc can't process your FX fast enough.

Giving sonar more time by raising buffers should help the dropouts.

You can also try the bypass all FX button.

Are you using soft synths? Check the processor levels in the control bar. Are you pegging the first processor?

Remember you can freeze tracks and synths to reduce processing during playback.

I always get the occasional dropout with X1, X2, and now X3. No processor heavy action going on here, it just decides to quit for no apparent reason. X3 actually crashed on one occasion. I run a lot of soft synths and this will happen whether they are frozen or not.
 
Sometimes while editing or bouncing audio tracks I'll get some scratchety popping static that may or may not clear up on it's own.
 
I've played with the buffer settings but haven't found a solution to this yet.

In addition to finding the appropriate ASIO buffer setting consider increasing the DropoutMsec variable in AUD.ini. The AUD.ini may be editing in Preferences > Audio > Configuration File. To see the Configuration File option make sure the "Advanced" button at the bottom of the Preferences dialog is selected. Read about DropoutMsec here http://www.cakewalk.com/D...;help=INI_Files.6.html

Thanks all!

I also discovered that I had the HD Audio driver that Craig Anderton was talking about. I thought I got rid of it, but NVIDIA's update installer must re-install it with updates.

(Now if I could understand the forum. I thought I had replied here, but didn't find my reply in the thread.)

All,

IO is probably a problem. When you stop recording, sonar releases file andorra you have a virus scanner it may scan the new wave for viruses. Sonar tests it to build a wave form.

If you start recording again, you may be competing with these processes to read all the audio from the disk.

Read that hd driver thread carefully. I did not disable out myself.

Again, thanks for all the replies.

Am I right in thinking that no one has experienced what I'm talking about? I.e., there have been several very good suggestions, but no one has said, "Oh yes, that used to happen to me and I fixed it with >>>X<<<".

I have had something like it happen when using synthesizers where the build up of processing on the synth slowly outgrows my processor's ability to keep up. This is especially true with certain synth patches that take more resources than others.
 
I cannot think of a case were amount of processor resource consumption slowly grows using audio tracks only (no midi).