Rendered freeze files in Pro Tools 12.6

[LSinBTonez]

Hey, I'm still new to Pro Tools. I wanted to know if there was a way to get pro tools to automatically delete the freeze files from the Rendered Files folder after unfreezing. I've looked in the manual and nothing about that was stated.


Sent from my iPhone using Tapatalk

[Drew Mazurek]

Originally Posted by LSinBTonez

Hey, I'm still new to Pro Tools. I wanted to know if there was a way to get pro tools to automatically delete the freeze files from the Rendered Files folder after unfreezing. I've looked in the manual and nothing about that was stated.

PT should "clean up" after itself when you close the session.

[LSinBTonez]

I just tested it again, the freeze file still remained. This is what I did to test it...

1. Froze a track then saved and closed the session.
2. Opened the session back up unfroze the track then saved and closed the session.

Then I checked the Session folder, it was still there.

[Drew Mazurek]

Originally Posted by LSinBTonez

I just tested it again, the freeze file still remained. This is what I did to test it...

1. Froze a track then saved and closed the session.
2. Opened the session back up unfroze the track then saved and closed the session.

Then I checked the Session folder, it was still there.

Shouldn't happen.

Log it as a bug on http://protools.ideascale.com if you like.

[LSinBTonez]

Thanks, will do now. I'm not trying to waste storage space.

[Drew Mazurek]

I logged it with Avid internally as well.

[Carl Kolchak]

I thought the fact that Pro Tools keeps all the frozen files is a feature, rather than a bug.

It's handy to have the various iterations of any frozen file, you never know when you may need to revert back to a previously frozen version - particularly when collaborating (you can send a specific rendered version to someone, who may not even be a Pro Tools user, carry on working on the unfrozen track, and still go back to an earlier frozen state if needed), or if you are using a modulation effect which is random in it's nature, and one particular freeze was more satisfying than subsequent others).

Each time a file is frozen, it is given a unique ID, but it's up to the user to log the takes.

Then again, it could be a bug...

Personally, when I come to archive a session, I go the "Save Copy In" route, and omit / clear out all the redundant data, which would take care of this issue.

The only trouble is, these days it's becoming the norm for a session to never be truly finished with - there always seem to be revisions somehow - so it's harder to get rid of the bloat, because you never know if it will eventually be required.

[Drew Mazurek]

Bug for sure.

What you're describing is what Commit is for.

[LSinBTonez]

I mainly use freeze if I'm heavy into mixing and I have to record some more tracks. And being that its rendering 32bit files that adds up pretty quick to just sit there.


Sent from my iPhone using Tapatalk

[Carl Kolchak]

Originally Posted by Drew Mazurek

Bug for sure.

Good to know - I thought it odd initially, but saw the usefulness.

Originally Posted by Drew Mazurek

What you're describing is what Commit is for.

Sure, except it actually works as a version log for freeze - I often find that even though I've progressed through a composition / mix, there are reasons that I want to go back to an earlier version of a frozen track (temporarily, or just for reference).

The advantage of Freeze, and the benefit of the stored rendered files, is that I don't have Commit creating new tracks - I can use the original tracks, and playlists.