Only the active rackspace and the Global Rackspace use CPU.
But, if you use multiple instances of ram heavy (sample based) songs, the ram add up.
So, if you reuse the same ram heavy sound, you might want to consider putting that in the Global Rackspace (there are other strategies to limit ram use as well).
Jeff
I would suggest you handle all volume related issues within GP, mostly using mixers in each rackspace.(Some people also add gain block too.)
There’s a great 6 channel mixer widget I use with every rackspace. I always add that. (Connect to the mixer block).
That way you can fine tune relative volumes in each song part. Amazing!
Jeff
Hi Jeff, thats what i’m doing. Doesnt matter if its a single vst or multiple vst into one rackspace, gain blocks are assigned for individual sound. I did create variation with different widget parameter which is good and cpu friendly solution… Regarding CPU, there’s nothing to worry about. I also have an observation about the RAM.
My gig file has 20+ rackspaces… mostly are Korg, Kontakt, Pianoteq… On Global rackspace Tokyo down Limiter and Valhalla reverb…
I see a spike of ram accumulation if i load Arturia collection. Then the ram comes down again even if i double the racksapce with Arturia… Same thing doesnt happen with Korg collection… (of course nothing comparable) OK, so i did a lot of adjustments between different VSTS while looking at the activity monitor…
FInally with 20 rackspaces and global racksapce, the total memory was 12 GB, GP 11.5 GB…
I closed the laptop and next day opened up the same gig file… GP was 8.9 GB and total was 9.something GB… I guess Apple has their own way to optimize the ram usage.
My take is that we really dont need to worry that much about the RAM or CPU usage… Let the machine do the job for you… Just be cautious a bit when you’re using a lot of sample based VST… For me, i have stopped calculating and completely concentrating on the music.