How many of you guys do this to save CPU?

[Loren Littlejohn]

Freeze button here.

 

[Seth Munson]

ps: kontakt 4 is just bejond shit. It is so bad written, it destroyed my macbook pro cpu performance and even my macPro gets a noticable cpu hit.
I so can wait for slates own plugin with the new SSD

I run 4-5 instances of kontakt 4 in every project I do, and I have at least 5 songs in one session and I never have problems with kontakt.

For me it is crucial to print anything that uses my UAD card, which is pretty much everything. So there isn't anything that doesn't get printed.

1176 on main vocals, LA2A on layers and vocal backings, 1176 and LA2/3A all over the drums, preflex on bass, LA2A guitars (usually) and whatever comp seems needed for synths.

Like I said it's pretty crucial for me to print because that starts to add up quickly and bands usually don't like tracking with latency

 

[if6was9]

Only ever had to do this on one project. Had 9 songs in 1 project with all amps sims and there were 8 different guitar tracks (different tones, quad tracked in places) and lots of vocals. Got a bit too much for my system to handle but thats the only time it's happened. I normally track using only real amps and don't do tons of sample replacement so it's not usually an issue at all.

 

[greyskull]

been doing it for years...

 

[Mago]

all the time.
Freeze something to save CPU. I generally have NO midi stuff in mixing sessions, I simply dont like it.
I program drums in seperate sessions too and then bounce the files to wave to loud into the mixing session
same for keys
amp sims get frozen too after Im done dialing in the tone
this way also prefents me to change stuff a million time even if its allready nice sounding

 

[Jevil]

Been doing that since 1936.


And +1 to all Mago said.

 

[462studio]

I usually freeze instruments and tracks when things get pretty busy. Recently, Cubase bit me in a project and lost it's mind with a set of frozen instruments.

It was opening up with errors and forcing an unfreeze, but wasn't REALLY unfreezing the instruments and it looked like the entire project file got corrupted.

I ended up dumping everything out of the project in WAV format and re-creating it and then bouncing all the instruments down to stems instead of freezing them.

 

[funtez]

In my roughly 9 years in computer-based audio production, I still don't think I've ever run out of CPU. I always feel ignorant when people discuss this.

<<<ode to be this guy.haha most of us always find a way to max it out asap once a new machine is powered up..

in all seriousness i think this is a cool thread showing a brief overview of everyones ITB workflow and workarounds for power vs project. Also very impressed with the amount of guys whoom sound like they are running some serious power under the hood(a MUST have)-and mac power of course.

personally im just getting acquainted with nebula and the idea of pre mix processing with the tape and console emulations>bouncing and then working the mix from there>using logic node on one of my other machines if i'm running abnormal amount of soft instruments but generally track count & native plugs is a non issue here now most stuff is going 64bit. freeze if i have to. up the buffer 1st. some algo based reverbs seem to be less taxing than the convolution for the most part IMO

 

[Wise_One]

Hey guys this freezing thing seems awesome, I could definitely use it to save some CPU. What exactly is it? Just muting the tracks I don't want? (I actually do this when I don't want something to play back).

I'm using Reaper, I read something about a freeze button and print process. Is print just exporting the specific track?

 

[bryan_kilco]

muting the tracks I don't want? (I actually do this when I don't want something to play back).

NO WAY??!!?!!

Helps me out in Reaper when I render tracks with FX applied. I really dislike doing it, as I'm constantly adjusting tones .... but if it's that bad that it's giving me hell, I'll do it.

 

[guitarguru777]

Print or GTFO!

 

[locus_coeruleus]

Hey guys this freezing thing seems awesome, I could definitely use it to save some CPU. What exactly is it? Just muting the tracks I don't want? (I actually do this when I don't want something to play back).

I'm using Reaper, I read something about a freeze button and print process. Is print just exporting the specific track?

I can't remember exactly how I did it (I thing I had to install an action list or something), but read this: http://forum.cockos.com/showthread.php?t=44331

 

[jimwilbourne]

yeah dude.
I print everything at some point. sometimes more than once.

SSD gets dumped after I'm done editing.

I bounce down all my raw tracks. then I bounce down all my editing tracks. then I bounce down all my "mixed" tracks. this way I have each element at ever stage in the event I need to go back and change something or if I need to reference the tracks for the current or following projects.

 

[Wise_One]

Thanks man I'll give it a shot. It's not that I use tooooo many plugins but it seems they are many for my dualcore. I don't know why but my lead guitar chain seems to get too much CPU, and my bass chain.

 

[Jind]

What is Freezing? Easier for me to just cut and paste from the Sonar Reference Guide (this is what it is and what it can do in Sonar):

Freeze tracks and synths

The Freeze feature allows you to temporarily bounce your track, including soft synths and effects, to reduce the amount of CPU power needed. The Freeze feature also works for synths patched in the Synth Rack.

The following are the available commands for track freezing:

• Freeze Track. Bounces the audio in the track to a new audio clip or clips, applies any effects,
and disables the effects bin.

• Unfreeze Track. Discards the bounced audio, restores the original audio to the way it was before the last Freeze or Quick Freeze command, and enables the effects bin.

• Quick Unfreeze Track. Hides and mutes the bounced audio, restores the original audio to the way it was before the last freeze or quick freeze command, and enables the effects bin. Bounced audio is retained, however, and toggling between Quick Freeze and Quick Unfreeze should be
instantaneous.

• Quick Freeze Track. Only available after a Quick Unfreeze, the Quick Freeze function redisplays and unmutes the bounced audio instantaneously and disables the effects bin.

The following are the available commands for synth freezing:

• Freeze Synth. Audio from a soft synth is bounced and placed on the synth’s track. Output from the synth is disabled, as is the effects bin on the synth track.

• Unfreeze Synth. Discards bounced audio, enables the synth and track effects bin. Bounced audio is discarded, and will be re-bounced if you choose Freeze again.

• Quick Unfreeze Synth. Hides and mutes the bounced audio, enables the synth and track effects bin. Bounced audio is retained, and toggling between Quick Freeze and Quick Unfreeze should be instantaneous.

• Quick Freeze Synth. Only available after a Quick Unfreeze, the Quick Freeze function redisplays and unmutes the bounced audio instantaneously, disables the synth, and any effects on the synth track.

Note 1: An Unfreeze or Quick Unfreeze command restores the audio on a track to the way it was before the last Freeze or Quick Freeze command. Any editing you do to a frozen track is discarded when you Unfreeze or Quick Unfreeze the track.

Note 2: You control the bit depth of all rendering operations (bouncing, freezing, applying effects) in Edit > Preferences > File - Audio Data, in the Render Bit Depth field. The default value of 32 is the best for most situations. See “Bit depths for rendering audio” on page 1112 for
more information.

 

[Loren Littlejohn]

"The Freeze feature allows you to temporarily bounce your track, including soft synths and effects, to reduce the amount of CPU power needed. The Freeze feature also works for synths patched in the Synth Rack."

This is essentially the same way it works in cubase.

 

[crosstalk]

I really hope this is a feature in Reaper 4.

I know there are macros for Reaper 3 out there, but I've never had much luck with them. I hate having to render a stem track that takes 5 minutes and needing to do it multiple times. Way too time consuming. I used to use Adobe Audition (yuck) and it even had freeze. Freeze always took time, but was a fraction of the time as rendering. I'm not sure why that is.

 

[NSGUITAR]

Isn't freezing the same thing as printing/rendering?

 

[Ionei]

Pretty much have too.

Can't wait to get a new PC.

But I'll still print, just because it seems odd not to.

 

[462studio]

Isn't freezing the same thing as printing/rendering?

That's how I looked at it until Cubase totally fucking screwed me last week. Haha. Probably not Cubase' fault. This is a massive, MASSIVE, project. I was asking for it.