Any downside to freezing tracks?

[dg27]

Although I generally don't have too many issues with CPU power spikes and running out of power, once in a while it will happen on large projects where I have a lot of plugins. I've found it happens more often since I started using Waves CLA-76 and Abbey Road plates plugins.

I've found freezing tracks that are basically "done" generally resolves the issue.

Are there any downsides to freezing tracks? (I always freeze to include all inserts.)

When I am done and ready to bounce the whole project can I bounce with those tracks still frozen with no ill effects?

[cwsand]

I don't see how freeze tracks would be any less quality than using the plugins - it should be the same quality since they are 32-bit and should speed up an offline bounce due to less processing. The only downside I can think of is that it would use a little more hard drive space. If you A/B a mix using freeze and one without - there should be no difference.

[amagras]

Exactly. Freeze prints the track with all the processing to an audio file in your hard drive. Only downside I see is you can't cut/paste in that file.

[albee1952]

For me, I much prefer COMMIT(usually not the entire track, but up to a certain plugin). For instrument tracks, I commit the VI. For audio tracks, I generally leave the top insert open so I can use that for Melodyne, Waves Bass Rider(it works well to commit this before other plugins as it has a ton lf latency) and noise reduction(for buzzing guitar/bass tracks). Freeze works well enough, but as said, a frozen track can't be edited. If I think I may revisit something, when I commit it, I only make the original track inactive(but keep it on the screen until I know its done)

[dg27]

Thanks, all for your valuable input.

Hard drive space isn't an issue for me at all.

Freeze has cut down on instances of running out of CPU power. And another thing I like is that, say, if I have a lot of guitar tracks, I freeze them when they are "done." Sort helps me keep moving.

The only thing I have to do is A/B as cwsand suggested, because I have one pair of tracks that I swear sound different frozen than not.

Thanks again.

[amagras]

Some plugins offer the possibility to select different values of oversampling for render and playback so can have low CPU consumption when working on the song and full processing quality when exporting, this applies to freezeing as well.

[64GTOBOY]

Originally Posted by amagras

Some plugins offer the possibility to select different values of oversampling for render and playback so can have low CPU consumption when working on the song and full processing quality when exporting, this applies to freezeing as well.

I did not know this-thanks for the info

[musicman691]

Originally Posted by amagras

Some plugins offer the possibility to select different values of oversampling for render and playback so can have low CPU consumption when working on the song and full processing quality when exporting, this applies to freezeing as well.

Some BlueCat and FabFilter plugs have user selectable oversampling.

[amagras]

Originally Posted by 64GTOBOY

I did not know this-thanks for the info

Originally Posted by musicman691

Some BlueCat and FabFilter plugs have user selectable oversampling.

Add Cytomic & d16 to the list.

[64GTOBOY]

I have noticed it on Bluecat, have a few of those.