Why "freeze" an audio track?

Author
optimus
Max Output Level: -84 dBFS
  • Total Posts : 316
  • Joined: 2011/12/20 02:35:41
  • Location: Whyalla, South Australia
  • Status: offline
2014/04/22 11:07:48 (permalink)

Why "freeze" an audio track?

On this forum I often see reference to "freezing" audio tracks, usually in order to fix some problem in playback.
 
Now, my understanding of "freezing", is in relation to midi tracks, where the "freezing" is actually rendering the midi track to audio. So, why "freeze" an already audio track?
 
I have experimented with "freezing" audio but see no difference in the waveform or sound of the clip. It can't be to prevent further manipulation of the clip, because it can still be edited. So why?
 
What am I overlooking here?

Sonar Platinum, Cakewalk by Bandlab, Roland Octacapture, Windows 7, i5 processor, 8 Gb RAM, X_Touch
#1

10 Replies Related Threads

    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: Why "freeze" an audio track? 2014/04/22 11:19:51 (permalink)
    It will temporarily print any effects to the clip and disable them to free up resources. It's like an easily reversible bounce/render.
     
    Cheers.
    #2
    optimus
    Max Output Level: -84 dBFS
    • Total Posts : 316
    • Joined: 2011/12/20 02:35:41
    • Location: Whyalla, South Australia
    • Status: offline
    Re: Why "freeze" an audio track? 2014/04/22 11:48:37 (permalink)
    Doh, of course!
    Does it for midi, so makes sense to do it for audio as well.
    Thanks Beep
     

    Sonar Platinum, Cakewalk by Bandlab, Roland Octacapture, Windows 7, i5 processor, 8 Gb RAM, X_Touch
    #3
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: Why "freeze" an audio track? 2014/04/22 12:23:31 (permalink)
    No prob. I rarely use Freeze myself though. Mostly I just clone my tracks, delete all the extra takes and other gack then archive/hide the originals. For MIDI tracks I get it solid, clone, bounce and then archive/hide the originals. That way after I'm done writing/tracking I'm just working with the necessary material for mixing but can still go back if I need to. Might be a little weird but it works for me.
     
    Cheers.
    #4
    Shambler
    Max Output Level: -75 dBFS
    • Total Posts : 783
    • Joined: 2010/07/06 05:20:19
    • Status: offline
    Re: Why "freeze" an audio track? 2014/04/22 13:21:26 (permalink)
    I've never had to freeze any tracks so far, this may change now I have u-he diva although I can run about 6 instances before hitting CPU overload...I do like to keep everthing 'live' so it can all be tweaked at any time.

    SONAR Platypus on Win10 64bit.
    Studio One Pro / Cubase Pro 9.5...just in case.
    8GB i7-2600 3.4GHz Gigabyte  Z68XP-UD3P
    Geforce GTX970
    Focusrite Scarlett 18i20 2nd Gen
    Prophet 12/Rev 2/Virus Snow
    Zebra2/DIVA/NI Komplete 10
    #5
    arachnaut
    Max Output Level: -67 dBFS
    • Total Posts : 1168
    • Joined: 2007/05/05 17:24:33
    • Location: Sunnyvale, CA USA
    • Status: offline
    Re: Why "freeze" an audio track? 2014/04/22 13:28:23 (permalink)
    When I need to freeze tracks I know it's time to buy a faster CPU.

    - Jim Hurley -
    SONAR Platinum - x64  - Windows 10 Pro 
    ASUS P8P67 PRO Rev 3.0;  Core i7-2600K@4.4GHz; 16 GB G.SKILL Ripjaws X;
    GeForce GT 740; Saffire Pro14 MixControl 3.7; Axiom 61
    64-Bit audio, SR: 48kHz, ASIO 256 samples latency, Rec/Play I/O Buffers 512k, Total Round Trip Latency 13 ms, Pow-r 3 dither 
    #6
    Beepster
    Max Output Level: 0 dBFS
    • Total Posts : 18001
    • Joined: 2012/05/11 19:11:24
    • Status: offline
    Re: Why "freeze" an audio track? 2014/04/22 13:41:39 (permalink)
    One thing that probably doesn't REALLY matter but tweaks at my crazy little brain is subtle changes in synth reaction during MIDI playback and delay/reverb type effects. Freezing/bouncing to lock all those kinds of things in place seems like a good idea for consistency while doing final mixing/eqing.
     
    I mostly just worry about my drum synths due to anti-machine gun settings and whatnot.
    #7
    slartabartfast
    Max Output Level: -22.5 dBFS
    • Total Posts : 5289
    • Joined: 2005/10/30 01:38:34
    • Status: offline
    Re: Why "freeze" an audio track? 2014/04/22 14:03:58 (permalink)
    I expect that in a couple of decades people will be asking, "Why would you put fuel in the car's gas tank?" Back in the dark ages when working with audio applications had to be interrupted for mastodon hunts, we used to need to freeze tracks so that the computer could do all the math without breaking the data stream.
     
    Arguably it would still be useful to bounce a track to audio, or freeze it if for example one of your live tracks had an effect with a look-ahead buffer, and you felt you really needed to hear that effect while recording or mixing real time without introducing unacceptable latency.
    #8
    optimus
    Max Output Level: -84 dBFS
    • Total Posts : 316
    • Joined: 2011/12/20 02:35:41
    • Location: Whyalla, South Australia
    • Status: offline
    Re: Why "freeze" an audio track? 2014/04/22 20:52:48 (permalink)
    Well, I thought I was missing something important, or doing things wrong. The type of music I do is mostly all audio with some midi piano and drums, which of course need to be frozen to be rendered to audio.
     
    I don't usually have high track counts and I don't normally have many plugins happening at once, so I have never run out of computing power. I guess I'll just carry on as normal until I hit the wall and then I'll know what to do.

    Sonar Platinum, Cakewalk by Bandlab, Roland Octacapture, Windows 7, i5 processor, 8 Gb RAM, X_Touch
    #9
    lawajava
    Max Output Level: -55 dBFS
    • Total Posts : 2040
    • Joined: 2012/05/31 23:23:55
    • Location: Seattle
    • Status: offline
    Re: Why "freeze" an audio track? 2014/04/22 21:44:32 (permalink)
    I freeze pretty much all tracks I'm not presently working on. It's just one click to either freeze or unfreeze to adjust as needed.

    Here's a simple example. Add an amp sim to a guitar track. Then pile on some effects within that amp sim. That can end up as a serious CPU hit for just that one track if you really take advantage of a bunch of the amp sim's features. But, if you freeze it you get all the sound without a hit on the CPU.

    Better yet, put the amp sim in an FX Chain bin in the ProChannel. Throw on some ProChannel modules and get the track sounding super awesome. Then freeze the track (one click). Again, you get all the super sound with no hit on the CPU. So including all the ProChannel processing and a full-on tricked out amp sim sound, you can end up with a simple audio track but which is totally optimized.

    Rinse and repeat throughout the tracks of the song. At the end you still have lots of CPU room to pile on live effects in the busses when mixing and even mastering.

    Two internal 2TB SSDs laptop stuffed with Larry's deals and awesome tools. Studio One is the cat's meow as a DAW now that I've migrated off of Sonar. Using BandLab Cakewalk just to grab old files when migrating songs.
    #10
    scook
    Forum Host
    • Total Posts : 24146
    • Joined: 2005/07/27 13:43:57
    • Location: TX
    • Status: offline
    Re: Why "freeze" an audio track? 2014/04/22 21:54:21 (permalink)
    Freezing or bouncing all tracks is also an archiving strategy. If the DAW, project or plug-ins fail at some future date the tracks can be imported into another project or DAW.
    #11
    Jump to:
    © 2025 APG vNext Commercial Version 5.1