Freeze Tracks with Garritan (or other VI)

[kschind]

I'm using GPO for several instruments in a MIDI realization of a piece and am having typical playback problems (processor overload, etc.). So I thought I'd freeze the tracks to free up the processor, then record the whole thing with the other MIDI tracks (with use regular sound modules). I'm just not sure how to do this freezing thing, though.

I have three GPO instruments with at least six sounds each, so I selected those tracks, then selected "Freeze Selected Tracks." The piece is 27 minutes and it took that long to freeze the three tracks. When it was done, though, it showed the three frozen tracks, but they are complely silent. The audio for the three tracks is just a solid line--no waveform at all.

What am I missing here? Do I create an aux track or something? I'm using 4.12 and my 4.0 manual doesn't meantion this, of course. The online help only describes the feature, but doesn't give any specifics.

I feel pretty silly asking, but I just can't figure out what I'm doing wrong.

[chrispick]

Actually, I don't recommend "freezing" your tracks.

One, as you've noticed, it doesn't save you any time because freezing in DP records the audio in real time. Why it doesn't work faster, like a bounce-to-disk function, I don't know.

Two, I find the freeze function engages badly from time to time, recording late or sometimes not at all (again, as you found out).

It's more reliable to create, arm and record onto a new stereo track. That is, create a new audio track, make sure its input matches the output of your VI (Garritan), then record onto it.

It's no faster than track freezing, but it always works. Good luck.

<small>[ April 13, 2005, 08:21 PM: Message edited by: chrispick ]</small>

[Morpheo]

Originally posted by kschindler:
The piece is 27 minutes and it took that long to freeze the three tracks. When it was done, though, it showed the three frozen tracks, but they are complely silent. The audio for the three tracks is just a solid line--no waveform at all.

You have to select both the MIDI tracks AND the instrument track. If you forget the instrument track, you get silence...

t's more reliable to create, arm and record onto a new stereo track. That is, create a new audio track, make sure its input matches the output of your VI (Garritan), then record onto it.

Which happens to be exactly how 'freeze tracks' are done, only the bus assignations are made on the fly by DP when you choose to freeze...

<small>[ April 13, 2005, 08:40 PM: Message edited by: Morpheo ]</small>

[Morpheo]

Originally posted by chrispick:
One, as you've noticed, it doesn't save you any time because freezing in DP records the audio in real time. Why it doesn't work faster, like a bounce-to-disk function, I don't know.

Because MIDI is not audio, MIDI triggers audio, which is quite a difference. The actual audio signal has to be recorded. That's why freezing tracks has to be done in real time. btw, freezing tracks can be very useful, especially with today's very cpu intensive VIs, such as Garritan...

[kschind]

Cool. Thanks, guys. I'll give it a try...and post my results in, say, 30 minutes.

[Morpheo]

Originally posted by kschindler:
Cool. Thanks, guys. I'll give it a try...and post my results in, say, 30 minutes.

Good luck !

[kschind]

Excellent! It worked. The problem was indeed that I hadn't selected the MIDI tracks originally, only the Garritan instrument track.

The only downside is that I need to record each instrument by itself, since freezing all three at once causes the same overload. So two more to go...and another hour.

Thanks for your help!

[chrispick]

Originally posted by Morpheo:

Originally posted by chrispick:
One, as you've noticed, it doesn't save you any time because freezing in DP records the audio in real time. Why it doesn't work faster, like a bounce-to-disk function, I don't know.

Because MIDI is not audio, MIDI triggers audio, which is quite a difference. The actual audio signal has to be recorded. That's why freezing tracks has to be done in real time. btw, freezing tracks can be very useful, especially with today's very cpu intensive VIs, such as Garritan...

I know the difference between MIDI and audio. Me got big brain go school third grade.

MIDI-to-audio-bounce should still be faster. It is in applications like Reason which will convert a MIDI sequence to an audio file in much-faster-than-real-time speed (including all applied automations and effects). It's a super-speedy process.

Also, if you record-arm multiple VIs instead of freezing them, you can record them all to track simultaneously. In my experience, freezing in DP can rarely handle more than a few VIs at once before clutching.

Apparently, freezing, then freezing again, then yet again is costing kschindler an hour's worth of extra waiting time. That's certainly not efficient, although he/she can have the joy of finishing taxes in that interim.

With an app like MachFive, I can set up multiple discrete outs for each patch. With record-arming, I can record each of those discrete outs to discrete ins -- in one record pass. Then, I save the Performance Set for each MachFive module, then clear the mothers out. Clean, simple, efficient, no do-overs.

Take my advice: Nix freezing.

<small>[ April 13, 2005, 09:59 PM: Message edited by: chrispick ]</small>

[Morpheo]

Originally posted by chrispick:
Me got big brain go school third grade.

...sorry...

[chrispick]

Originally posted by Morpheo:

Originally posted by chrispick:
Me got big brain go school third grade.

...sorry...

It's cool, daddy-o. I got love for everyone.