Frozen tracks = No tempo ruler editing

[blizzard]

I have just upgraded to 12.4 on my PC, and changed my composing template. I was previously using VEPRO to host all VI's, but now I'm freezing all VI's hosted within Pro Tools via the Track Freeze feature.

This is the error I get:

The tempo ruler cannot be edited because the session contains one or more frozen tracks. Unfreeze all tracks before editing the tempo.


A workflow killer I just came across during my first session was that I can't edit the tempo of the session if I have any frozen tracks. When you're using the Track Freeze feature to host a huge amount of VI's or plug-ins within Pro Tools, this can take a while. It also requires me to remember (or keep a list of) every track I unfreeze while composing with the template. The whole purpose of a template is to have everything ready at your fingertips and speed up the process. Not slow it down.

Anyways, just whining over here. Anyone have a similar issue and have found a decent workaround? Go back to using VEPRO?

Cheers,
Andrew

[clausiii]

It seems you need to commit tracks instead of freeze them if you want to edit the tempo ruler. Or you make a "freeze/unfreeze" group of selected tracks you need to unfreeze all at once, edit something and re-freeze them again.

[midnightrambler]

At least that one gives an error. Try duplicating or "consolidate all VCA automation" or any one of a thousand other commands and you'll get nada - no indication whether the command has worked or not. This has caught me out enough times to make sure I never use freeze for anything, other than as a strictly temporary measure.

[john1192]

since Slate SSD4 does NOT hold it's settings when using Make InActive / Make Active .. freezing does not work yet for SSD4 ... so i cannot Freeze, unfreeze and make changes .. i hope this is fixed soon ..

[albee1952]

To john1192, this is a different issue(belonged in its own thread), but your solution would be to save the settings as a preset in the plugin.

To blizzard, indeed, using Commit is the proper way to deal with this.

[daeron80]

That's expected behavior, though. There are only two logically possible alternative designs. 1) Allow tempo track editing to throw frozen tracks out of sync following the tempo change. 2) Make all frozen audio automatically be Elastic, which would consume vastly more processing power. IMHO, Avid chose the best option.