Freeze or Render?

[DWS]

Regarding the new Render Track option in the update (variable bit depth and sample rate), does 'Freeze Track' render at the highest available bit depth (since there are no options available for Freeze Track?)

In other words, if I freeze tracks am I getting the maximum or highest available depth?

-s

[rich_h]

Can't remember off hand, but all frozen tracks are recorded into the same file, which I think is 24 bit, whereas with render you're obviously getting individual audio each rendered track.

[DWS]

all frozen tracks are recorded into the same file, which I think is 24 bit.

I saw that in the user/reference guide but it did not specify what bit depth the 'one file' would be.

Anyone know for sure? In other words, is a freeze at 24 bit exactly the same as a track render at 24 bit in regards to the wav output? I would compare the files but don't know where the freeze files are. -s

[FoxV]

Relatedly, if you freeze a track, and then render the whole song, do you get the same end result as if you'd never frozen the track??

(sorry for piggybacking....)

[metamorphosis]

per-track freezing requested.
m@

[IIRs]

request denied

I'm pretty sure freeze files are 32-bit. (There never seems to be any headroom problem anyway )

[djsubject]

per-track freezing requested.
m@

its in there

just thay called it render & its permenent

the listed freeze is for a quick cpu fix while you work on somthing else

all frozen files are droped on closing a edit

NOTE, muteing a track, or a bus track with severail tracks feeding it will free up ALL resorses being used by that/those track/s

Subz

[IIRs]

NOTE, muteing a track, or a bus track with severail tracks feeding it will free up ALL resorses being used by that/those track/s

Except RAM I think..?

Still, good point Subz! If only you had the same sensible views about mixers..

[Lunch Money]

Except RAM.

But that's OK, it's the same as any other host. The only way to truly and permanently free up resources in any other host is to 'render'.

Some hosts have taken to cleverly calling their render function "freeze" so that it looks like a more feature-laden version of other hosts' freezes, but it's really just render. Since Tracktion already has render, you can always just use THAT.

I think it's 32-bit. Easy way to find out is to freeze some tracks and then look in the temp directory. There should be a corresponding .wav file in there, and if you hover over it, a tooltip should tell you the bit-depth I believe.

[IIRs]

Another test: select an audio clip and wack the gain up in the properties until you can hear really nasty distortion. Now turn down the master fader till the sound cleans up again. (it might take a while for the meters to catch up!) Now freeze the track.. afaik if the freeze file was less than 32-bit it would distort as badly as the output did before you turned the master down.

[djsubject]

As it turns out, a frozen file is ".freeze" and not ".wav". But, the whole project frozen is 53 MB, and the whole project as a stereo 32-bit export is 44-ish MB, so I guess it seems fairly safe to assume that it's 32-bit. If that's the case, I wonder what the other 10MB are for!

this was posted by greg in the wrong thread

Subz

[LBN]

I, too, would like to have a per-track freeze option. While the current freeze pool works well to save disk/CPU resources it's kind of a pain if you just want to unfreeze one track out of 20 frozen tracks because it has to again render the other 19 tracks. Sure, you can "render track -> add rendered tracks" but this leaves you with an audio file in your directory and you still have to manually mute the track or disable the VSTs -- not a very elegant solution for so elegant a program. I would like to see a freeze command with two options: Freeze-to-pool or freeze-to-individual-file. The freeze-to-individual-file would perform the same function as "render track->add rendered tracks->mute/disable VSTs" but would be a one-button affair and one-button to undo.

[mandolarian]

And we all love a good one-button affair...

[Neil G]

per-track freezing requested.
m@

the listed freeze is for a quick cpu fix while you work on somthing else

all frozen files are droped on closing a edit


Subz

do they. i couldve sworn if i freeze tracks, then close the program, the frozen tracks are still there when i re open.

[LBN]

And we all love a good one-button affair...