is there any difference in the processing power reduction between freezing an individual track and doing a straight bounce-down?
I've read that freezing is essentially a bounce down, where the new wav file replaces the track contents - though does it still eat up any extra CPU power to have the original stuff (be it MIDI or soundfile, and plugins) frozen in the background?
thanks!
Bounce vs. Freeze?
Re: Bounce vs. Freeze
No it´s basically the same thing.
Freeze has the advantage of still being able to unfreeze the tracks and edit settings but the projects can only be opened in Live.
Bouncing your tracks is final but then you have the advantage of being able to import the tracks into another DAW for further mixing or mastering.
Freeze has the advantage of still being able to unfreeze the tracks and edit settings but the projects can only be opened in Live.
Bouncing your tracks is final but then you have the advantage of being able to import the tracks into another DAW for further mixing or mastering.
-
- Posts: 1135
- Joined: Mon May 31, 2010 12:36 pm
- Contact:
Re: Bounce vs. Freeze?
And bouncing gives you a mono option. Freeze/flatten always renders stereo or double mono files.