Quote:
Originally Posted by Extreme Mixing
Use Commit. It creates an audio file that becomes a permanent part of the session. Freeze makes a temporary audio file that disappears when you, or someone else un freezes the track. That can be inconvenient if you are not expecting it.
And, yes it can save resources. If you are using, say Trillian for bass, playing back the audio file is a lot less DSP intensive than having the instrument up.
Steve
|
Going along with that advice, Commit gives the option of keeping the the original track in an inactive state.
So you could opt to commit even on a temp basis and reactivate the original track if need be.
*Tip: Make sure to establish all your tempos before temporarily freezing too. Otherwise you'll have to unfreeze & re-freeze everything to adjust tempos while recording and that can interrupt a good recording vibe & workflow.
I use the Trilian bass module also. Sometimes two instances for different sections. Rock & Synth Bass trade offs!
As JFreak mentioned, I'll commit the instrument only to free up resources and THEN insert plugins on the committed track.
That way I have a "lighter" audio clip of the bass track that I can still experiment with plugin-wise (as the mix changes) or apply clip gain & fades during the mix phase.
When VI drums are done, I'll commit multi-output to separate audio tracks. Again, just the instrument plugin and maybe a limiter.
That way I can remix and save various versions of the unprocessed committed tracks.
After my instrument tracks are done, I usually have enough resources for mix plugins and would only need commit again if exporting as session stems.
Whether you choose to freeze or commit, restarting Pro Tools frees up the RAM allotted to previously active instrument plugins.