Freezing Audio tracks seems a very slow process...
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
-
- Posts: 599
- Joined: Sun Feb 20, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: san antonio TX
Freezing Audio tracks seems a very slow process...
... 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?
Thoughts?
----------------------------------
Mac Pro (early 2009 - originally 4,1 - flashed to 5,1) 2 x 3.42 GHz 6-Core Xeon X5690, 64 gigs PC3-10600 RAM, OS 10.13.3, DP9.52, UAD2 duo, UAD2 solo,
Superior drummer 2, Mach 5-3, Ivory, PCIe 424, BL modded 24i/o, MIDI express XT, unisyn, Melodyne 2, Izotope RX2, Addictive Drums, Pianoteq
Mac Pro (early 2009 - originally 4,1 - flashed to 5,1) 2 x 3.42 GHz 6-Core Xeon X5690, 64 gigs PC3-10600 RAM, OS 10.13.3, DP9.52, UAD2 duo, UAD2 solo,
Superior drummer 2, Mach 5-3, Ivory, PCIe 424, BL modded 24i/o, MIDI express XT, unisyn, Melodyne 2, Izotope RX2, Addictive Drums, Pianoteq
- MIDI Life Crisis
- Posts: 26254
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Freezing Audio tracks seems a very slow process...
Freezing is essentially realtime bouncing. Bouncing takes less time. Freezing always processed realtime.
- buzzsmith
- Posts: 3097
- Joined: Mon Dec 27, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Houston
- Contact:
Re: Freezing Audio tracks seems a very slow process...
Yep.MIDI Life Crisis wrote:Freezing is essentially realtime bouncing. Bouncing takes less time. Freezing always processed realtime.
Early 2009 Mac Pro 4,1>5,1 3.33 GHz Hex Core Intel Xeon OS X 10.8.5 SSD (32 gigs RAM)
DP 9.51 PCI-424e / original 2408, 2408mkII, 24I/O, MTP-AV
Yamaha C7 Conservatory Grand
Hammond B-3 / Leslie 145
Focal Twin6 Be(s)
DP 9.51 PCI-424e / original 2408, 2408mkII, 24I/O, MTP-AV
Yamaha C7 Conservatory Grand
Hammond B-3 / Leslie 145
Focal Twin6 Be(s)
- doodles
- Posts: 732
- Joined: Sun Oct 17, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Scotland / LA
- Contact:
Re: Freezing Audio tracks seems a very slow process...
yep. read manual if you want full explanation, but freezing IS realtime - you can't make it go faster.
2*5-core 3.46 Intel xeon (32 gigs RAM), 2*dual 2.5 (16 & 32 gigs RAM), DP 8.07, WAVES 9, Lexicon plugs, SoundToys, all Spectrasonics, NI Komplete 9, Vienna Ensemble (extended), LASS, Evolve, Symphobia, etc, Cinesamples, Arturia, cinestrings, all Project Sam
- MIDI Life Crisis
- Posts: 26254
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Freezing Audio tracks seems a very slow process...
There's a manual?
-
- Posts: 599
- Joined: Sun Feb 20, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: san antonio TX
Re: Freezing Audio tracks seems a very slow process...
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.doodles wrote:yep. read manual if you want full explanation, but freezing IS realtime - you can't make it go faster.
----------------------------------
Mac Pro (early 2009 - originally 4,1 - flashed to 5,1) 2 x 3.42 GHz 6-Core Xeon X5690, 64 gigs PC3-10600 RAM, OS 10.13.3, DP9.52, UAD2 duo, UAD2 solo,
Superior drummer 2, Mach 5-3, Ivory, PCIe 424, BL modded 24i/o, MIDI express XT, unisyn, Melodyne 2, Izotope RX2, Addictive Drums, Pianoteq
Mac Pro (early 2009 - originally 4,1 - flashed to 5,1) 2 x 3.42 GHz 6-Core Xeon X5690, 64 gigs PC3-10600 RAM, OS 10.13.3, DP9.52, UAD2 duo, UAD2 solo,
Superior drummer 2, Mach 5-3, Ivory, PCIe 424, BL modded 24i/o, MIDI express XT, unisyn, Melodyne 2, Izotope RX2, Addictive Drums, Pianoteq
-
- Posts: 599
- Joined: Sun Feb 20, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: san antonio TX
Re: Freezing Audio tracks seems a very slow process...
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.MIDI Life Crisis wrote:Freezing is essentially realtime bouncing. Bouncing takes less time. Freezing always processed realtime.
Okay - I'm going to read the manual now (something I do everyday now)
----------------------------------
Mac Pro (early 2009 - originally 4,1 - flashed to 5,1) 2 x 3.42 GHz 6-Core Xeon X5690, 64 gigs PC3-10600 RAM, OS 10.13.3, DP9.52, UAD2 duo, UAD2 solo,
Superior drummer 2, Mach 5-3, Ivory, PCIe 424, BL modded 24i/o, MIDI express XT, unisyn, Melodyne 2, Izotope RX2, Addictive Drums, Pianoteq
Mac Pro (early 2009 - originally 4,1 - flashed to 5,1) 2 x 3.42 GHz 6-Core Xeon X5690, 64 gigs PC3-10600 RAM, OS 10.13.3, DP9.52, UAD2 duo, UAD2 solo,
Superior drummer 2, Mach 5-3, Ivory, PCIe 424, BL modded 24i/o, MIDI express XT, unisyn, Melodyne 2, Izotope RX2, Addictive Drums, Pianoteq
- MIDI Life Crisis
- Posts: 26254
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Freezing Audio tracks seems a very slow process...
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.zandurian wrote:Then why would anyone ever freeze instead of bounce?
-
- Posts: 599
- Joined: Sun Feb 20, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: san antonio TX
Re: Freezing Audio tracks seems a very slow process...
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?MIDI Life Crisis wrote: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.zandurian wrote:Then why would anyone ever freeze instead of bounce?
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.
----------------------------------
Mac Pro (early 2009 - originally 4,1 - flashed to 5,1) 2 x 3.42 GHz 6-Core Xeon X5690, 64 gigs PC3-10600 RAM, OS 10.13.3, DP9.52, UAD2 duo, UAD2 solo,
Superior drummer 2, Mach 5-3, Ivory, PCIe 424, BL modded 24i/o, MIDI express XT, unisyn, Melodyne 2, Izotope RX2, Addictive Drums, Pianoteq
Mac Pro (early 2009 - originally 4,1 - flashed to 5,1) 2 x 3.42 GHz 6-Core Xeon X5690, 64 gigs PC3-10600 RAM, OS 10.13.3, DP9.52, UAD2 duo, UAD2 solo,
Superior drummer 2, Mach 5-3, Ivory, PCIe 424, BL modded 24i/o, MIDI express XT, unisyn, Melodyne 2, Izotope RX2, Addictive Drums, Pianoteq
- mikehalloran
- Posts: 15231
- Joined: Sun Jan 25, 2009 5:08 pm
- Primary DAW OS: MacOS
- Location: Sillie Con Valley
Re: Freezing Audio tracks seems a very slow process...
I think iBounce is $1.99 in the App Store.Or is that iBounce?
DP 11.31; 828mkII FW, micro lite, M4, MTP/AV USB Firmware 2.0.1
2023 Mac Studio M2 8TB, 192GB RAM, OS Sonoma 14.4.1, USB4 8TB external, M-Audio AIR 192|14, Mackie ProFxv3 6/10/12; 2012 MBPs Catalina, Mojave
IK-NI-Izotope-PSP-Garritan-Antares, LogicPro X, Finale 27.4, Dorico 5.2, Notion 6, Overture 5, TwistedWave, DSP-Q 5, SmartScore64 Pro, Toast 20 Pro
2023 Mac Studio M2 8TB, 192GB RAM, OS Sonoma 14.4.1, USB4 8TB external, M-Audio AIR 192|14, Mackie ProFxv3 6/10/12; 2012 MBPs Catalina, Mojave
IK-NI-Izotope-PSP-Garritan-Antares, LogicPro X, Finale 27.4, Dorico 5.2, Notion 6, Overture 5, TwistedWave, DSP-Q 5, SmartScore64 Pro, Toast 20 Pro
- doodles
- Posts: 732
- Joined: Sun Oct 17, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Scotland / LA
- Contact:
Re: Freezing Audio tracks seems a very slow process...
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.
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.
2*5-core 3.46 Intel xeon (32 gigs RAM), 2*dual 2.5 (16 & 32 gigs RAM), DP 8.07, WAVES 9, Lexicon plugs, SoundToys, all Spectrasonics, NI Komplete 9, Vienna Ensemble (extended), LASS, Evolve, Symphobia, etc, Cinesamples, Arturia, cinestrings, all Project Sam
- MIDI Life Crisis
- Posts: 26254
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Freezing Audio tracks seems a very slow process...
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.
- doodles
- Posts: 732
- Joined: Sun Oct 17, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Scotland / LA
- Contact:
Re: Freezing Audio tracks seems a very slow process...
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.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.
2*5-core 3.46 Intel xeon (32 gigs RAM), 2*dual 2.5 (16 & 32 gigs RAM), DP 8.07, WAVES 9, Lexicon plugs, SoundToys, all Spectrasonics, NI Komplete 9, Vienna Ensemble (extended), LASS, Evolve, Symphobia, etc, Cinesamples, Arturia, cinestrings, all Project Sam
-
- Posts: 599
- Joined: Sun Feb 20, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: san antonio TX
Re: Freezing Audio tracks seems a very slow process...
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.doodles wrote: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.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 don't know what the freeze/bounce capabilities of Mach 5 v3 are because I haven't even installed it yet.
----------------------------------
Mac Pro (early 2009 - originally 4,1 - flashed to 5,1) 2 x 3.42 GHz 6-Core Xeon X5690, 64 gigs PC3-10600 RAM, OS 10.13.3, DP9.52, UAD2 duo, UAD2 solo,
Superior drummer 2, Mach 5-3, Ivory, PCIe 424, BL modded 24i/o, MIDI express XT, unisyn, Melodyne 2, Izotope RX2, Addictive Drums, Pianoteq
Mac Pro (early 2009 - originally 4,1 - flashed to 5,1) 2 x 3.42 GHz 6-Core Xeon X5690, 64 gigs PC3-10600 RAM, OS 10.13.3, DP9.52, UAD2 duo, UAD2 solo,
Superior drummer 2, Mach 5-3, Ivory, PCIe 424, BL modded 24i/o, MIDI express XT, unisyn, Melodyne 2, Izotope RX2, Addictive Drums, Pianoteq
- MIDI Life Crisis
- Posts: 26254
- Joined: Wed May 18, 2005 10:01 pm
- Primary DAW OS: MacOS
- Contact:
Re: Freezing Audio tracks seems a very slow process...
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!