Track Freeze vs Track Commit

[Tom Graham]

Originally Posted by volodia

The other advantage I see is : if you have native plugs on tracks inducing delay and you want to do a quick overdub , you just freeze them for the recording and recover them afterwards

I agree - especially fast and useful if you are at the end of a mix and need to cut one new part.

[DonaldM]

Thanks for the insights. Looking forward to getting 12.4 and using it.

[Shan]

Originally Posted by DonaldM

I'm not sure that it speeds up workflows all that much though. We're talking nanoseconds here.

Try a multi-output VI like a drum kit. Make a simple drum fill change after using Commit. Areas like that is where the Commit workflow falls apart. Even changing a small part of the arrangement would end up being very procedural and long winded. Every minute saved keeps me creating and in the groove. The last thing I want to do in the creative phase is fumble around with track management in a DAW. PT has many groove killers that are in need of a few simple revamps.

Shane

[DonaldM]

Originally Posted by Shan

Try a multi-output VI like a drum kit. Make a simple drum fill change after using Commit. Areas like that is where the Commit workflow falls apart. Even changing a small part of the arrangement would end up being very procedural and long winded. Every second saved keeps me creating and in the groove. The last thing I want to do in the creative phase is fumble around with track management in a DAW. PT has many groove killers that are in need of a few simple revamps.

Shane

I can see that. I didn't realize that freeze would allow you to freeze individual outputs of multi-output VIs like a drum kit. It'll be fun to begin playing with it once its here. They're saying "late" December....

[Shan]

Here's an old list of where track freeze would be used and very useful in PT. It's not just for saving CPU usage as many assume:

http://duc.avid.com/showpost.php?p=2147836&postcount=20

Shane

[littlesicily]

Originally Posted by volodia

The other advantage I see is : if you have native plugs on tracks inducing delay and you want to do a quick overdub , you just freeze them for the recording and recover them afterwards

Agree, this will be useful.

[DonaldM]

Originally Posted by Shan

Here's an old list of where track freeze would be used and very useful in PT. It's not just for saving CPU usage as many assume:

http://duc.avid.com/showpost.php?p=2147836&postcount=20

Shane

Good list, thanks. I noticed you mentioned normalization spikes with SansAmp. I've used SA a lot and I don't recall one time having that particular issue.

[midnightrambler]

Well, I have to say, now I've got both, I find myself using Track Commit over Track Freeze almost every time. Maybe I just haven't got Freeze properly embedded in my workflow yet.

Anyone here actually using Track Freeze in preference to Track Commit?

[Drew Mazurek]

Originally Posted by midnightrambler

Anyone here actually using Track Freeze in preference to Track Commit?

Two different things. Two different uses.

Freeze is great for tracks you're not done with and would like to able to revisit, but would like to knock down latency or CPU in the meantime.

Commit is for tracks you're finished with and you want to future proof them while simultaneously saving some CPU and latency. Or be able to send a "finished" track without the other person needing your plugs etc.

No need too prefer one over the other.

[DonaldM]

Originally Posted by midnightrambler

Well, I have to say, now I've got both, I find myself using Track Commit over Track Freeze almost every time. Maybe I just haven't got Freeze properly embedded in my workflow yet.

Anyone here actually using Track Freeze in preference to Track Commit?

I find myself using both. As Drew said, two different uses. What I have found is that using commit more or less forces me to consider that track "done", whereas with freeze it is still a concept in progress. I like having both and no question it helps with the CPU!