Bug, or feature? Freezing isolated tracks

[audiopimp]

I've used busses as far back as I can remember, and when my cpu starts creaking I've just frozen the busses I'm not working on to free up some cpu cycles.

But I recently updated to the new version, Pro Tools 23.3, and now it seems I'm unable to freeze tracks that are on 'input monitor'

Any ideas? Is this something Avid instigated deliberately, or is this a bug?

[Darryl Ramm]

You mean you freeze aux tracks? If an aux has no signal feeding it what does freezing it mean? I've never tried freezing one without that before and I'd have never expected it to work. If you have extra tracks not doing stuff, and presume plugins on the track that are consuming CPU just make those tracks inactive, or try dynamic plugin processing and see if that helps.

[Sardi]

Are you sure you don’t mean commit track not freeze track?

You can definitely commit an Aux track but as Darryl pointed out, I don’t think you can freeze an Aux track as there is no audio on the timeline.

I could be mistaken on the latter as I don’t really use freeze. I do use commit though and use it to render Aux busses all the time.


Sent from my iPhone using Tapatalk

[midnightrambler]

You can freeze aux tracks.

I think we need to know what the OP means by "isolated tracks".

[Darryl Ramm]

Originally Posted by Sardi

You can definitely commit an Aux track but as Darryl pointed out, I don’t think you can freeze an Aux track as there is no audio on the timeline.

You sure can freeze an Aux track if it has content... meaning there is something upstream feeding it. (but then that also leaves the source track(s) live being processed and sending stuff out... so often that will want to be manually frozen as well).

I cannot fathom what freezing an aux track with no content means or why not being able to do that would be an issue.

And yes I also have no clue what "isolated track" means here either.

[audiopimp]

Apologies for my stupid nomenclature. Isolated; My bad, let's correctly call it INPUT MONITOR.

Using audio tracks as busses (as opposed to using aux tracks), I put them in 'Input monitor', route a bunch of stuff to them (with some heavy CPU plugs) and previously to this latest version, you could FREEZE so it renders a temporary audio file, thus freeing up the CPU.

There's no audio file on the input track, just a bunch of feeds from channel & fx routing