Gearslutz (
-   Ableton Live (
-   -   How freezing and rendering really works? (

owly 29th December 2019 03:12 PM

How freezing and rendering works inside?
Does anyone know how freezing/bouncing/rendering really works "inside the box"?
For example: What is the flow for resulting audio file when you recording vst+midi to internal track or freezing it?

Does it affected by ... > CoreAudio/ASIO/MME > Audio Interface > ... ?
Or everything will be done by CPU, so you'll get same results on any configuration?

Thanks! peachh

pottering 29th December 2019 07:58 PM

It is done "by CPU", you get the same results on any configuration.

owly 30th December 2019 01:30 AM

And that is great,
So, to summarize:
  1. Audio interface affects only external monitoring and recording by DAC.
  2. Drivers like CoreAudio, ASIO, WDM, MME or WASAPI affecting only latencies between card and OS.
    Although, WDM can introduce some additional aliasing at monitoring if sample rate conversion occurs.
  3. DAW channels and mix processed internally by "transparent math".

Also, after some additional googling I have found several similar topics:
Thanks! peachh

Mikael B 31st December 2019 12:14 AM


Originally Posted by owly (Post 14412703)
DAW channels and mix processed internally by "transparent math".

32-bit float in Live. However, if you're recording internally and the Bit Depth settings of Live are at 24-bit, the recording will be saved as 24-bit integer and when processed again the audio stream will be automatically improved to 32-bit float, as that is what Live runs at.

This works so well, that an unprocessed 24-bit integer recording of a 32-bit float source, will null completely with each other (if played back in perfect sync and at the same level) even as the bit streams are maintained in each track.

A frozen/flattened file is 32-bit float on disk.

At the audio interface of course you're likely truncating to 24-bit for the monitoring.