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.