Freeze Tracks in MC3

Although page 69 of the MC3 "Getting Started" manual states that the Freeze function is not available, I found that it is - it's just not called "freeze" and it doesen't have a single (snowflake) process button.

In the clips view, select a clip, click in the FX box and add the effect and tweek it to your liking. Now all you have to do is go to the Process dropdown menu and select Apply Audio Effects.

Man, you gotta' love MC3!

MC3s' Process>Apply Audio Effects dialog states "APPLY AUDIO EFFECTS - This will apply the audio effect(s) from the track inserts to the selected track" - that's a freeze.

Dialogue continues with "(Check box that is default checked) - Delete the effects from the track inserts" - this gives one the option of leaving the insert effects inline after the freeze, or deleting them from the track after the freeze. (Use this option creatively for full unfreeze capability).

Last paragraph of dialogue states "Undoing the effect will not restore the effects to the track inserts" - This dialogue means that if you decide to unfreeze a track(s), you will permanently loose the effect(s) settings before the freeze on THAT track - that's a semi-functional unfreeze. (This is where MC3 lacks the convenience of an integrated, one-button freeze/unfreeze function).

Actually, there is a creative work around that will give you full freeze/unfreeze functionality but I'll let you figure that one out on your own.

MC3 has full freeze/unfreeze capability, it's just requires a couple of extra mouse clicks!

That's my story and I'm stickin' to it!

Yes, obviously you could save your settings as a preset, then delete during the PROCESS AUDIO step. So, you're right, you can use this process as a freeze by performing those steps.

I think joe's pretty much nailed the spirit of it, tho.

Dog - That's not what I had in mind.

444 - I think most would agree that a fully undoable freeze function is really special as it frees up precious little CPU resources.

Robo - Processing 32 tracks of controllerless MIDI is roughly the equivalent of a single .wav audio track. I'm not sure what you mean by: "Then as far as the audio effects just buss them and it saves on the resources anyway." - I don't see your connection between routing and freezing/unfreezing. Although this technique does free up memory-based resources, these are minisule compared to processing digital data from a HDD.

1) Duplicate the effected track.
2) Archive the duplicated track.
2) Freeze the track.
3) To unfreeze - Archive the current track and unarchive the track duplicate.

Get it?

Like I said, a couple of extra mouse clicks and you have full freeze/unfreeze functionality within MC3

Dog - ^ see edited post ... "these are minisule compared to processing digital data from a HDD". You state - "If you're using it as a temporary means of saving resources, it won't really matter, but if you keep them archived like that permanently, you'll start to eat up hard drive space."

I would recommend that you keep all the tracks until you've completed the project - after all, you may need to unfreeze a track and make some changes! When the project is complete bundle it and offload it to a DVD or your favorite backup sub-system. Naturally, you would then delete the bundle from your working HDD.

My point is this midi tracks take almost no resources, unless you use softsynths then they soak up the CPU in bunches, and by bouncing to audio and muting the midi tracks the load lightens. Then you can still save the whole bundle, but you can also delete the midi and save as a new file. Then you can work strictly with audio, which is far easier on the load, and much better to run though effects especialy when the effects are properly bussed. I usually save a midi only, a mixed midi and audio and an audio only multitrack, with a final mixed down Wave and MP3 file on DVD for my archive disc.

I think that is exactly what he means, only a few have a dedicated freeze button, one i have is N-Tracks studio. but ultimately all freeze means is that it allow one to lighten the load of the softsynths. I use Multitrack studios a lot and all i do is bounce or off line mix a softsynth track to an audio track and it is the same thing. Acid will do it by doing a render to tracks featureAt least on the Pro, maybe not the studio version

Joe - I'm still not convinced that you're with me on this?

Most will agree that freeze/unfreeze relates to inline effects.

Robos' description a few posts back about rendering softsynth MIDI tracks to digital audio tracks is the perfect anology.

Freeze is a technique similar to rendering a softsynth/MIDI track to digital audio, however, freeze is different as it is a method of rendering a track with inline effects to a single audio track so you can remove the processing overhead caused by said effects.

In summation:

MC3 docs do indicate that MC3 DOES NOT have freeze capability.
I have discovered that MC3 DOES have freeze capability via a simple easy workaround.

If you don't agree with my summation, please explain.

My point is you can't claim that MC has freeze when you're going the long way around to do the process.

What you're saying is one can't claim to have climbed Mt Everest if it was accomplished traveling via New York City?

Right. It's like claiming MC has automation recording when you're using a mouse to edit envelopes.

How about calling it an Oven? since this subject was a hot one.

Go to the top of this thread and read the original post. I think you'll agree that I said it's not called freeze.

Although page 69 of the MC3 "Getting Started" manual states that the Freeze function is not available, I found that it is - it's just not called "freeze" and it doesen't have a single (snowflake) process button.

joe - thanks for all your help with nomenclature and definitions, etc - As a result of all joes' hard work, I think it should be calld the joeh20_444 deep freezer technique! - LOL!


shubitty - zippiditty - fashashatyif! - WTF!

Has anyone seen the price of eggs lately?