|
Freeze function in Ableton Live 5
|
View this Thread in Original format
| Thois |
So how is it (good/bad/etc) and do you guys use it?
Just curious (i want to move to Ableton one of these days) |
|
|
| retrobyte |
it's a welcome addition to the feature set in Ableton, but it has a couple of flaws. it works well enough, but it doesn't turn off the VSTs in use, so if you have 16 frozen tracks using VSTs, they're still idle instances of the VST is use, so it really doesn't help much if you have about 20 tracks.
It helps, but the only way to do render the track, turning off the vst, and putting the wav into another audio track. they say they're working on improving it for the next 5 version (thankfully)! |
|
|
| rbrown46 |
I use it alot, but like the above post stated, there are problems with it:
- Occassionally, the freeze files will disappear, as documented here, which is really annoying because you have to re-freeze every track upon opening a set.
- The tracks are really frozen. I would prefer it if I could manipulate the audio after I freeze a track (kind of like a quick bounce to audio on top of the midi track). If I want to add some simple automation or bring a track out a measure before, why should I have to unfreeze, do the change (which could be done with audio), and then wait for it to do the freeze again?
- When I do drums, I like to use one instance of Battery 2 (Native Instrument's drum sampler), with multiple MIDI tracks being piped into it (one for high hat, one for BD, etc.). The track running Battery doesn't actually have any MIDI data on it. I'd like to be able to freeze that drum track, but there isn't any way to do it that I've found. It can only take the MIDI data from the track you are attempting to freeze.
From my experience, it does deactivate Audio Units, but it may just be that the idle CPU usage is negligable. I'll test it later. On a positive note, freezing a track is much faster than manually playing a whole track into audio, which is amazing to me. I know that it can cut areas of silence by just skipping through them, but it also manages to get all the release effects after a midi note is released w/o a problem. It also seems to be faster than real time on tracks w/o silence, which I have no idea how it does. |
|
|
|
|
