Freezing

[meister eder]

get your analogy but I think this is shakey ground. You'd get disqualified for showing up on a motorcycle, but if you were allowed to race, you would blow everyone away. In software, you don't get disqualified for having more capability. Don't get me wrong, I see your point...I just don't completely agree with you. If giving me the ability to actually DO something with my frozen data is diluting freeze, then I guess I like my freeze slushy

I guess my whole point is that of how to name it. I think the "expanded" freeze just shouldn't be called "freeze", because it is another function (although technically about the same). But I said that already.
No question that those are great options, and I wouldn't reject having them. But I said that already, too. So I better shut up now.

[Jaeson Merrill]

It's just counter-productive.

If you want to do something with it, don't freeze it... just render it and have done.

Greg

but when you render it, how do you put in the rendered file??? and then how do you disable the effects?? and how do you remove the vstis???

lots of extra clicks!!

and then, lets say you want to alter it after a while..

how do you delete the file you put it??? click click..
how do you re-enable all the effects.??? click click.. how do you restore all the vstis??? click, wait for it to load, find the fxb you hopefully saved of that exact preset you had before..

buggery i tell you!

[Lunch Money]

It's just counter-productive.

If you want to do something with it, don't freeze it... just render it and have done.

Greg

but when you render it, how do you put in the rendered file??? and then how do you disable the effects?? and how do you remove the vstis???

lots of extra clicks!!

and then, lets say you want to alter it after a while..

how do you delete the file you put it??? click click..
how do you re-enable all the effects.??? click click.. how do you restore all the vstis??? click, wait for it to load, find the fxb you hopefully saved of that exact preset you had before..

buggery i tell you!

Really?

I didn't know. In Tracktion, you just press "render and replace". One click.

As for if you want to make changes or not, hey I agree that freeze is useful. I just don't think that farting around with "frozen" tracks is really freezing anymore. Hence, I'd go to the 'tiered' freezing system I've already mentioned. You can't ignore earlier points just because of a new one.

Or, for only a few more clicks, render to a new track (rather than replace) and mute the old one. Again, if you want to make changes (and do so with the rendered track) then the tiered freezing system I mentioned comes in handy again.

Greg

[tony tony chopper]

and it doesnt take THAT long.

no need to argue about this, it's just logic. If something eats 50% CPU, then it will eat 50% of the playing time to render.

now, if there were freezing options on fxracks,

it would definitely work on mixer tracks in FL

How about a simple macro that will render a mixer channel that has been armed to record, drop the resulting audio clip in the playlist, and then turn off all effects for that armed channel and any instruments associated to that mixer channel? Is that basically what you had in mind?

more or less. You ALREADY have a macro that renders and put the result in the playlist.
The idea is to:
-mark that playlist clip as 'frozen / temporary'
-whenever that playlist clip is playing, all of the effects/generators linked to that mixer track will stop being mixed
-unfreezing a part will just mean deleting the frozen clip

So you'll be able to freeze one part of the song, then the rest will still play realtime, and for the frozen part, it's the audio clip that will play instead. This will have the downside that plugins will have to be kept, not unloaded, since they will still be useful to the song.

[Jaeson Merrill]

[quote="gol]
So you'll be able to freeze one part of the song, then the rest will still play realtime, and for the frozen part, it's the audio clip that will play instead. This will have the downside that plugins will have to be kept, not unloaded, since they will still be useful to the song.[/quote]

well the most important part of the freezing is the automated loading and unloading of plugins..

being able to unload a generator and bring it back with one click with the same xcat preset .

[tony tony chopper]

well the most important part of the freezing is the automated loading and unloading of plugins..

the most important part? well then I think I'll give up with freezing, because I naively thought it was about saving CPU..

[Igor 4000]

well the most important part of the freezing is the automated loading and unloading of plugins..

the most important part? well then I think I'll give up with freezing, because I naively thought it was about saving CPU..

I'm quite sure he was referring to the freezing process. Otherwise without all the automated loading and unloading, you just have manual rendering.

[Jaeson Merrill]

well the most important part of the freezing is the automated loading and unloading of plugins..

the most important part? well then I think I'll give up with freezing, because I naively thought it was about saving CPU..

good lord gol..yes thats the BLOODY point

lets as a couple of easy questions.

1. how can we save cpu?

a. by rendering cpu intensive generator tracks to audio.

2. but what about the plugins and generators left behind?

a. the plugins can be disabled, and so can the generators.

3. but what about generators that still take up cpu if theyre disabled?

a. we can unload them

4. but if we unload them, how can we get them back? i dont want to have to program that patch again, or even take the time to make an .fxb or anything, im lazy?!?!

a. thats ok, be lazy, you worthless sack of crap, we can unload the plugin and remember what setting it had, and everything else about it. then we can restore it with the same settings with a click.

5. ok even still, what about all those plugins i have to disable??

a. well, we can do it for you, when you select an fx rack to be frozen.

6. what about when i want them back?

a. read answer to question 4 again.

7. what if i have a generator that is being sent to an fxrack?

a. any fxrack that has freeze selected will find which generators have been sent to that track and apply them to the freezing process. (in other words, an fxrack will have to have the generators frozen as well)

8. what if i have generators that i want to freeze that are being sent to a particular fxrack?

a. when you freeze it, the audio will stream into that fxrack still from an audiotrack channel or otherwise (freeze channel?), we'll do all the work behind the scenes, its ok


9. what if i link a knob from one generator being frozen to another not being frozen?

a. youre screwed, basically; just dont be a moron and do that. (we'll think of something better soon)

--freeze out

[tony tony chopper]

I'm quite sure he was referring to the freezing process. Otherwise without all the automated loading and unloading, you just have manual rendering.

I won't bother then.. I don't much believe in what's to spare by unloading plugins, unless those plugins are crap.

[Jaeson Merrill]

gol youre a stubborn guy.. its not just about unloading plugins.... but that is something you need to do... its what every freeze process does!!

samplitude, cubase, not sure avout tracktion, fxfreeze... theres aREASON for it...

duh... man, too l337 for me guess...

[Jaeson Merrill]

you know also,

heres where you go horribly wrong..

generators that use RAM.

THE ONLY WAY TO TRULY DISABLE THEM IS TO UNLOAD THEM FROM MEMORY.

or do you just use ts-404... think, gol!

[tony tony chopper]

3. but what about generators that still take up cpu if theyre not disabled?

you mean 'if they're disabled'?
Well, they shouldn't. How/why would they if FL doesn't process them anymore?

Note that you can't disable generators in FL (yet). You can only mute them, that is, stop their scoring. Muting them would cut remaining sounds.

Unloading plugins will only spare RAM and loading time, but will make freezing/unfreezing even more long & painful.

[Jaeson Merrill]

duh, yes gol, youre right, i mean if they are disabled...

ok, well theres a step then.

is there a way to TRULY disable generators?

[Jaeson Merrill]

cause that could mean the difference right there...

i mean, sure you wouldnt save on RAM, but at least you could REALLY disable plugins, like how effects work..

[tony tony chopper]

ok so it's

well the most important part of the freezing is the automated loading and unloading of plugins..

and 2 posts later it's

gol youre a stubborn guy.. its not just about unloading plugins....

That's why I don't think I'm gonna bother - it would work but most people wouldn't understand it.
I ran a poll in the FL forum not so long ago anyway, the results weren't that convincing.
I would find it cool to be able to freeze parts of the song, but if that means complaining that generators can't be unloaded..