There is no reason to unfreeze before a final mixdown. Frozen audio is stored as floating point data so there is no loss of resolution compared to the synth.
BTW there is an audio snap command that allows you to "un audiosnap" clips from the AS toolbar I think. That should get rid of the extra processing passes if the audio snap operation was unintended..

I believe freezing was created to free up system resources, for projects with lots going on, or systems that are RAM limited. When using frozen tracks, it enables you to keep latency at maximum levels, if you need to record something live, or play in a new part to a complex project.

If your latency is good, no dropouts as the project progresses, then I think it's true . . . you may never need to freeze any of your tracks.

Yes, the only time I freeze these days is if my system is struggling to keep up with all that Midi data being processed.

Some people like to freeze their synths once tracking/recording has finished so that when you're mixing, you are working totally in the Audio world, not Midi.

It might be prudent to freeze your synths whenever a project is 'finished' (define finished ) and to save the resulting audio only project down with a different name, just in case you decided to re-visit it at some time in the future and you find that a particular synth is no longer on your system.

Bristol_Jonesey

It might be prudent to freeze your synths whenever a project is 'finished' (define finished ) and to save the resulting audio only project down with a different name, just in case you decided to re-visit it at some time in the future and you find that a particular synth is no longer on your system.

+1. Freezing a project before archiving it is your best insurance against a synth getting obsolete. I do this on every project of mine. Lets say you want to  open up that project 5-10 years from now for a remix or some reason. You have a new OS new machine and the old crusty synth no longer exists. You have all you need to work with that project again. Unfreezing gives you back the MIDI data should you need to reassign it to a different synth.
Another good reason to freeze - an update to a synth may change the way it sounds which could be a problem if you have a finished project and just need to remix. Also some synths generate non-deterministic output which can vary slightly on each bounce.

Or in SONAR you can use the quick unfreeze feature to quickly audition differences between a prior part and a new one. Many reasons to freeze besides saving CPU. 


Edit: I missed another very good reason to freeze. Stability! Once you freeze you have completely eliminated all the DSP code in the synth from running. So you are completelu insured against any bugs in the synth (crashes, memory leaks, heap corruption) from causing instability in your SONAR project. Once you get to the mixing stage there is seldom any need to tweak any parameters related to the synth so freezing allows you to work with just the audio and a completely stable inside DAW only environment.

FastBikerBoy

Teds_Studio


BTW....what is the reason for freezing if you need to unfreeze before mixing down?  Is it to free up processing power of the DAW?  I have a fairly powerful PC especially for doing audio....it works fine for working on HD video which I also do on this same PC, so I would think it would handle audio with ease.

So if I understand this right...I really have no need to freeze anything unless my PC is getting bogged down?

Correct.  
edited to fix typo

Ted,you shouldn't have to freeze with an i7 2600k cpu,but about the "no audio pop up" if you select File/Export/Audio,I sometimes get that,and for me it only happens on my laptop[dell xps-a bit buggy] and if I save/reopen it will then usually be nice enough to get me to the "Export Audio" box,and when I'm there I usually select "Source Category"-Entire Mix,"source Busses/Tracks"-Audio Output.

Often I have it "blank" for "preset",and all the usual 16 bit 44.1 "dither" Power 3,and 64 bit Engine,the thing with this laptop[that may be occurring with yours as well ?] is I have to make sure the destination in Windows is correct as THAT will often be in-correct,so I must choose "libraries" etc,just like if I want a Pro Channel preset the wrong page opens[always on laptop] and I must find that.

Then its just press "Export",and it usually goes fine.

If I'm doing anything wrong here,someone let me know,Thanks!

Bob

Edit: I Totally missed Sir Noel's other myriad of reasons to freeze,so sorry about that,I generally haven't had much synth stuff happening,exept for Drum/soft synth,and I still have'nt bounced or frozen there yet[bounced yes,frozen no]

No problem ........

g_randybrown

This is very valuable info for me.... I had old projects (PA 9) I wish I would have at least saved the midi files...I'm now recreating them from scratch from a stereo wav. 
Just to make sure I completely understand this procedure of archiving I would save as a cwb right?

Randy

X2 will read even PA9 files so you should get all your MIDI tracks back intact as long as you have the .wrk or .bun files.
There is no need to save as a cwb. You can save as per project audio files and then archive the entire project folder. Thats actually the preferred way. 

seems to me bounced tracks get saved, "frozen" track are not saved (deleted when "unfrozen").

BTW, Sonar Plus's BULK FREEZE still works in X1D, just so you know. Just make sure all folders are expanded as it won't freeze any tracks hidden inside a collapsed folder. I still don't get why Cakewalk doesn't just give us a Bulk Freeze option, Benstat nailed it years ago!
 
This might have been mentioned here somewhere, but the other reason to freeze ALL tracks and BOUNCED busses is for archiving reasons - it saved my bacon on more than one occasion when a client suddelny wants a remix or a backtrack and the plus have become obsolete!