So now that Sonar Plus has really become unuseable and unaintained, my Bulk Freeze is also gone....

Does anyone know which variables are the most useful to tweak in order to speed up freezing tracks in X1?

(And before anyone asks, I run massive mixes with Slate VCC etc etc, 18 busses, external sends etc etc. - that's why I have to freeze :O)

Hi Ludwig, I saw the following approach to try and solve your problem in the SWA Complete SONAR X2 tutorial video, purchaseable through the Cakewalk E-Store: in the Preferences menu-> Configuration File-> BounceBufSizeMSec-> try changing this value from 100-350 and see how that works out for you.

Ludwig, have you tried freezing your soft synths, rather than the tracks?

Thanks Mike-  I've experimented with those before, but it still takes long to render each track.

As for freezing just synths, most of my work is made up of real instruments, so though I do freeze synths they are the least of the problem. The issue comes in with running a 60 or 80 track mix with 6x Oversampling activated in Slate VCC, realtime inserts and heaps of plugins. It's just a huge amount to demand from my PC (i7 2600 with 8 GB Ram) and popping and clicking becomes an issue.. 

No problem, Ludwig. I understand... Do you think the solution to this particular problem may be that it's time for an upgrade? With those numbers you gave, I'm surprised your PC hasn't melted already! I have more than enough trouble already with much smaller projects than that, running 16GB RAM and very good (can't remember exact product name) i7s...

Hmm.

My old DAW was capable of running a 75 track project, mutiple (100+ plugins), multiple live V-Vocal clips, and this was on an XP32 machine with 4Gb of RAM

I don't think his machine is a problem.

Mea maxima culpa... Then I'm afraid I'm stumped.

Slate VCC DOES eat tons of CPU in oversampling mode. Maybe that's the difference?

Something like V-Vocal for instance does not take any CPU - it renders a new wav, AFAIK.

Maybe some part of my system is inferior... not sure what RAM is in there - Kingston or Corsair, most likely..

You do have fast-bounce enabled under Freeze Options, right?

If so, try un-checking the "FX" option in Freeze Options and see if that speeds the process. It could be a plugin that's slowing it down.

LJB


Slate VCC DOES eat tons of CPU in oversampling mode. Maybe that's the difference?

Something like V-Vocal for instance does not take any CPU - it renders a new wav, AFAIK.

Maybe some part of my system is inferior... not sure what RAM is in there - Kingston or Corsair, most likely..

My suggestion here is simple: run VCC at No or 2x oversampling in realtime, and set it to a higher setting for Offline/Render. This way, when you're mixing, you'll hear the effect and save a ton of CPU, then on render, you'll get the benefits of oversampling. This is why many plugins now have two different settings (playback vs. render). It will seem like you have plenty of additional CPU available to you.