bitflipper

Looks like another good reason to stick with good ol' reliable bouncing instead of freezing---I never got why the latter was supposedly preferable anyway.

I love the freeze feature and use it often. It's all about speed and convenience. It's not just the convenience of freezing over bouncing; much more valuable is the convenience of quickly un-freezing when you need to tweak something.

Freezing isn't always about saving CPU cycles, either. Here's an example of how I used the freeze feature just the other day, to quickly extract a hit from a drum track.

I wanted one snare hit to have a big reverb tail on it - just the one hit. Now, I could have automated the reverb but that would be inefficient, CPU-wise. So I froze the drums, highlighted the one hit and ctl-dragged it into another track where I could apply the reverb as a clip effect and bounce it. Now I've got big reverb on one snare hit with no extra CPU overhead. A quick unfreeze of the synth and I'm back to editing mode.

There are actually 2 things I dislike about freezing: 1- The color of the track that's frozen is ALWAYS white ..ugh. 2- If you unfreeze often, Sonar will crash.

bitflipper

There are actually 2 things I dislike about freezing: 1- The color of the track that's frozen is ALWAYS white ..ugh. 2- If you unfreeze often, Sonar will crash.

Haven't experienced point #2, but agree with the color complaint. By the time I get to the final mix stage, my larger projects have all turned monochromatic. It would be nice if there were some other way to indicate a frozen track and leave the colors intact.