Logic Pro 8 Protect vs Freeze

Made To Feel

Made To Feel

Logician
Hi - What's the difference between the freeze & protect settings? Also, which if any would best apply to my situation: I'm scoring a 5 min video with multiple cues. I've completed the first section and want to disable as many possible changes to those tracks as I can (automation, regions, mix volumes) before I go on to the second. Thanks!
 
Sort by date Sort by votes
If you have multiple cues, definitely split them into multiple sessions. You can bring in the bounce of an earlier/later cue if you want to see how they go together.
 
Upvote 0
Thanks for the reply, pkm. Just curious, is this generally how it's done or are there any dissenters from this? I understand the reasoning in keeping separate sessions, but find it easier sometimes if I'm using similar setups.

Regardless I'm still curious what the difference is between freeze and protect.
 
Upvote 0
I don't use protect, so I don't know.

I've never worked with a composer who did every cue in one session. Better to save channel strip settings and templates if you want similar sounds. The only exception is in DP. They have a feature called Chunks that can separate cues within one project file, and it's pretty great.

But in general, way too much can go wrong with one session.
 
Upvote 0
A nice work flow is to do a save as at the end of the cue you've just worked on and name it for the next cue. Delete all your regions in the newly created project, and the rest of your Channel Strip settings are alreay in place and you are ready to start working on the next cue once you set the new smpte start time. You can even save it to the same project folder. That way all your cues/projects will access the same pool of samples and audio files, in case you re-use some from cue to cue.

Freeze renders a temporary 32 bit audio file comprised of the data that is on the track that's frozen. It saves cpu resources by freeing up demands for the heavy processing that might be on the track that is being frozen (if it uses lots of plug-ins. But it also places greater demands on the hard drive throughput, since it is now reading a 32 bit audio file. So, it is better for cpu mileage, but harder on the hard drive. The conventional wisdom is to only freeze tracks that use a lot of plug-ins, and only do it if you are reading/writing your audio files to a separate drive. Protect merely protects regions from accidentally being edited on the tracks that are "locked".
 
Upvote 0
Back
Top