Remove distinction between FREEZE and FLATTEN
Posted: Mon Oct 25, 2010 1:50 pm
! Thanks
Kevin Rothi wrote:I think a better way to implement this would be to have something in the rightclick context menu that would allow the user to just skip the freeze step and just go to flatten directly. Keep freeze in there, too, because sometimes it's useful for CPU conservation and a couple other things.
yeah I wouldn't like to lose freeze, most of the time I use it for creating clips by option + dragging the frozen clip to a new audio track (which effectively flattens it) so I can create a number of clips from the same track. I wouldn't want to have to set up a new track each time when at the moment I just 'unfreeze' then carry on until I want to make another clipKevin Rothi wrote:I think a better way to implement this would be to have something in the rightclick context menu that would allow the user to just skip the freeze step and just go to flatten directly. Keep freeze in there, too, because sometimes it's useful for CPU conservation and a couple other things.
this.Kevin Rothi wrote:I think a better way to implement this would be to have something in the rightclick context menu that would allow the user to just skip the freeze step and just go to flatten directly. Keep freeze in there, too, because sometimes it's useful for CPU conservation and a couple other things.
I think what's actually sought here is having flatten available without having to freeze first. The the two are related, but by no means the same thing, so removing the distinction between them is not the solution.33tetragammon wrote:this.Kevin Rothi wrote:I think a better way to implement this would be to have something in the rightclick context menu that would allow the user to just skip the freeze step and just go to flatten directly. Keep freeze in there, too, because sometimes it's useful for CPU conservation and a couple other things.
they should keep both.
Not completely different, they both render the track to WAV. The same thing. The only difference is that in Freeze the instruments are kept in memory wasting RAM. I'm not aware of any difference in the WAV produced by Freeze and the WAV produced by Flatten. Maybe you know of one?sporkles wrote:I think what's actually sought here is having flatten available without having to freeze first. The the two are related, but by no means the same thing, so removing the distinction between them is not the solution.33tetragammon wrote:this.Kevin Rothi wrote:I think a better way to implement this would be to have something in the rightclick context menu that would allow the user to just skip the freeze step and just go to flatten directly. Keep freeze in there, too, because sometimes it's useful for CPU conservation and a couple other things.
they should keep both.
Both create wave files, correct, but the two have rather different purposes: freeze "suspends" the devices, so as to freeSimbosan wrote:
Not completely different, they both render the track to WAV. The same thing. The only difference is that in Freeze the instruments are kept in memory wasting RAM. I'm not aware of any difference in the WAV produced by Freeze and the WAV produced by Flatten. Maybe you know of one?
If you did what I suggest you would have all the advantages of Flatten but without losing your midi.
I could be missing somethin, I'm relatively new to Ableton...
S
Yes I know what they do, and the chopping freezing can be done with a frozen track, just drag it to another track and bingo. I am saying that the 'suspend' device call should also 'unload' the device so that you get BOTH the CPU saving AND the RAM saving AND you don't have a destructive edit AND you have the WAV so you can chop it about as a new track if you wish AND you no longer have any real need for Flatten.sporkles wrote:Both create wave files, correct, but the two have rather different purposes: freeze "suspends" the devices, so as to freeSimbosan wrote:
Not completely different, they both render the track to WAV. The same thing. The only difference is that in Freeze the instruments are kept in memory wasting RAM. I'm not aware of any difference in the WAV produced by Freeze and the WAV produced by Flatten. Maybe you know of one?
If you did what I suggest you would have all the advantages of Flatten but without losing your midi.
I could be missing somethin, I'm relatively new to Ableton...
S
up CPU, whereas flatten is final; it ditches the devices originally in the track, and, leaves you with only the rendered
file. Freeze's only purpose is to free up resources, but Flatten can also be used creatively, for chopping, stretching and
mangling the resulting file. So what you're suggesting should instead be incorporated into Freeze, while Flatten should be
kept, but moved up at the same level as Freeze, so you didn't have to go through Freezing first.
what makes you think it's wasting all this RAM? are you having specific problems that make you think RAM is being wasted? I'm not sure this is the case at all, or if it is it is negligible.Simbosan wrote:Yes I know what they do, and the chopping freezing can be done with a frozen track, just drag it to another track and bingo. I am saying that the 'suspend' device call should also 'unload' the device so that you get BOTH the CPU saving AND the RAM saving AND you don't have a destructive edit AND you have the WAV so you can chop it about as a new track if you wish AND you no longer have any real need for Flatten.sporkles wrote:Both create wave files, correct, but the two have rather different purposes: freeze "suspends" the devices, so as to freeSimbosan wrote:
Not completely different, they both render the track to WAV. The same thing. The only difference is that in Freeze the instruments are kept in memory wasting RAM. I'm not aware of any difference in the WAV produced by Freeze and the WAV produced by Flatten. Maybe you know of one?
If you did what I suggest you would have all the advantages of Flatten but without losing your midi.
I could be missing somethin, I'm relatively new to Ableton...
S
up CPU, whereas flatten is final; it ditches the devices originally in the track, and, leaves you with only the rendered
file. Freeze's only purpose is to free up resources, but Flatten can also be used creatively, for chopping, stretching and
mangling the resulting file. So what you're suggesting should instead be incorporated into Freeze, while Flatten should be
kept, but moved up at the same level as Freeze, so you didn't have to go through Freezing first.
S
hmmm.. ok, just never noticed a problem myselfSimbosan wrote:RAM is what instruments use when they are loaded in memory. When a track is Frozen, the instruments are NOT unloaded, and the RAM used by instruments is not negligible, you think Omnisphere has a light footprint? Why would you think instruments have negligible memory footprint?
I have spoken to Abes about this very point, I am 100% sure that a frozen track uses the same RAM as an unfrozen one, if not more (cos of the extra ram for the wav).
S
You just don't seem to get the point, which is: sure, your 'unload from RAM' suggestion is all fine and dandy, but what we'reSimbosan wrote:Blah