Page 1 of 4

Freezing Audio tracks seems a very slow process...

Posted: Sat Mar 02, 2013 8:49 pm
by zandurian
... in fact I found that freezing single audio tracks with a Melodyne plug inserted is pretty much a real time affair as a 5 minute song takes about 5 minutes to freeze. To test whether Melodyne was involved I opened a small (30 audio tracks - no VIs) project just to test the freeze speed and freezing a mono track with NO EFFECTS at all took just as long! I really would expect a faster freeze with a 2009 eight core computer with 12 gigs of RAM running 64bit with an SSD bootup drive and 7200 RPM project hard drive. The CPU and playback seem to be idling along under no duress whatsoever. I even disabled all tracks except for the one I was freezing and still pretty much the same result.

Thoughts?

Re: Freezing Audio tracks seems a very slow process...

Posted: Sat Mar 02, 2013 8:57 pm
by MIDI Life Crisis
Freezing is essentially realtime bouncing. Bouncing takes less time. Freezing always processed realtime.

Re: Freezing Audio tracks seems a very slow process...

Posted: Sun Mar 03, 2013 6:51 am
by buzzsmith
MIDI Life Crisis wrote:Freezing is essentially realtime bouncing. Bouncing takes less time. Freezing always processed realtime.
Yep.

Re: Freezing Audio tracks seems a very slow process...

Posted: Sun Mar 03, 2013 4:21 pm
by doodles
yep. read manual if you want full explanation, but freezing IS realtime - you can't make it go faster.

Re: Freezing Audio tracks seems a very slow process...

Posted: Sun Mar 03, 2013 4:27 pm
by MIDI Life Crisis
There's a manual? :shock:

Re: Freezing Audio tracks seems a very slow process...

Posted: Sun Mar 03, 2013 6:27 pm
by zandurian
doodles wrote:yep. read manual if you want full explanation, but freezing IS realtime - you can't make it go faster.
Wow - I had no idea and still have no idea why that would be. I guess the manual will explain that too. Except I probably won't take the time since I have to read it in real time. :oops:

Re: Freezing Audio tracks seems a very slow process...

Posted: Sun Mar 03, 2013 6:32 pm
by zandurian
MIDI Life Crisis wrote:Freezing is essentially realtime bouncing. Bouncing takes less time. Freezing always processed realtime.
Then why would anyone ever freeze instead of bounce? Is these an old feature from when early VIs could not be bounced in anyway except in real time? I think I first started using freeze when a bounced superior drummer2 bounced track was off but the freeze was tight. Yet the manual claims bouncing will work with VIs and it mostly does but the superior drummer thing proved not always.

Okay - I'm going to read the manual now (something I do everyday now)

Re: Freezing Audio tracks seems a very slow process...

Posted: Sun Mar 03, 2013 6:35 pm
by MIDI Life Crisis
zandurian wrote:Then why would anyone ever freeze instead of bounce?
It used to be that you couldn't bounce a VI but you could freeze it. Some people think bouncing not as reliable as realtime, so you have an option. I bounce. Or is that iBounce? iDon'tKnow.

Re: Freezing Audio tracks seems a very slow process...

Posted: Mon Mar 04, 2013 4:14 am
by zandurian
MIDI Life Crisis wrote:
zandurian wrote:Then why would anyone ever freeze instead of bounce?
It used to be that you couldn't bounce a VI but you could freeze it. Some people think bouncing not as reliable as realtime, so you have an option. I bounce. Or is that iBounce? iDon'tKnow.
It is more reliable with certain VIs which I guess makes it the VIs fault? But freeze or bounce should (ideally - apparently not in DP) happen as fast as the drives and processor are capable of freezing or bouncing without introducing problems, right?

So my guess is that Freeze exists as a slow, plodding way to get plugs with sucky bounce behavior to be bounce to audio. Make sense?

I used to just arm tracks and record them real time as the song played. At least that way if it screwed up I wouldn't have to listen to the whole song again to find out the bad news.

Re: Freezing Audio tracks seems a very slow process...

Posted: Mon Mar 04, 2013 5:05 am
by mikehalloran
Or is that iBounce?
I think iBounce is $1.99 in the App Store.

Re: Freezing Audio tracks seems a very slow process...

Posted: Mon Mar 04, 2013 3:54 pm
by doodles
here's an example of when you would freeze:

Take a finished sequence containing 25 or 30 instances of VI's. (eg. VE Pro, Omnisphere, etc). Each has 16 mini channels. You want to print all the MIDI into individual audio channels to take to an external studio to mix. If you bounce, unless you've got some MAJOR routing going on, you would have to bounce 1 track at a time. With freeze, you can select 1 MIDI channel from EACH VI (25 or 30) and freeze all at once. Saves a •••• load of time. Crashes DP half the time though when you do too many at once. :lol:

Re: Freezing Audio tracks seems a very slow process...

Posted: Mon Mar 04, 2013 4:37 pm
by MIDI Life Crisis
Too bad that we can't freeze/bounce multi channels of all VIs to their respective tracks. UNless I'm missing something, unless you have that elaborate routing system in place, BTD on VI mixes the MIDI channels for that instantiation of the VI.

Re: Freezing Audio tracks seems a very slow process...

Posted: Mon Mar 04, 2013 4:45 pm
by doodles
by MIDI Life Crisis » 05 Mar 2013 12:37 am

Too bad that we can't freeze/bounce multi channels of all VIs to their respective tracks. UNless I'm missing something, unless you have that elaborate routing system in place, BTD on VI mixes the MIDI channels for that instantiation of the VI.
i know. I keep meaning to start a thread to get people's input on best way to do it, as tracklaying for soundtracks takes forever. I WISH there was a way just to freeze all tracks selected at once, no matter how many MIDI channels going to each VI. There's obviously a reason why not, I just can't think. It would save literally days.

Re: Freezing Audio tracks seems a very slow process...

Posted: Mon Mar 04, 2013 7:23 pm
by zandurian
doodles wrote:
by MIDI Life Crisis » 05 Mar 2013 12:37 am

Too bad that we can't freeze/bounce multi channels of all VIs to their respective tracks. UNless I'm missing something, unless you have that elaborate routing system in place, BTD on VI mixes the MIDI channels for that instantiation of the VI.
i know. I keep meaning to start a thread to get people's input on best way to do it, as tracklaying for soundtracks takes forever. I WISH there was a way just to freeze all tracks selected at once, no matter how many MIDI channels going to each VI. There's obviously a reason why not, I just can't think. It would save literally days.
In the past I've taken all the vi tracks, multitrack drum VIs etc and and bussed them to real audio tracks, arm and hit record. Of course the problem comes in when you have one multi-timbral VI doing a bunch of stuff to stereo outs. With Mach 5 2 I just open multiple instances and keep it one instrument per instance but that's a bit nuts.

I don't know what the freeze/bounce capabilities of Mach 5 v3 are because I haven't even installed it yet.

Re: Freezing Audio tracks seems a very slow process...

Posted: Mon Mar 04, 2013 7:50 pm
by MIDI Life Crisis
On a multi-core machine each instance of a VI gets a difference core so as MagicD says: spread the wealth! One instrument per instance is good!