I have a gig file with 17 rackspaces (one per song) and that takes up ~8GB of memory. Luckily I have a relatively new MBP with 64GB RAM, but it does seem high. I do have a brass patch that is a combination of Kontakt Session Horns and three Zenology instances, and that one was copied to each rackspace.
I suppose the more efficient way to do that would be to load that horn combi into a global rackspace and assign to it in each rackspace (song) where it is needed?
I started working with GP1/2 and found an easy way of working before Global Rackspace and Rig Manager was a thing.
It has one but the forum system doesnât let users edit their posts until they have been around for a certain amount of time. Designed to prevent spamming
Iâve upgraded you manually to regular member so you should now be able to edit
Ok but why do you care if you have 64Gb of RAM and youâre only using 16GB? What else do you need your RAM for during your show? Are you planning on reading your email and surfing the web or playing games while youâre performing?
Thatâs kind of a a serious questionâŚwhy the need to conserve RAM in this situation?
Actually, itâs not a problem at all. I wasnât even thinking about it until I read this thread and decided to check Activity Monitor to see how big this particular Gig file is.
And no, during shows I have everything turned off, obviously.
But I guess Iâm from the oldskool, from a time when we really needed to manage memory and storage, so some of that mindset prevails.
Nevertheless, memory usage has not been a problem for me. Even five years ago with GP2 on a dualcore MBP with 8GB RAM.
Well, even today, the documentation for an upcoming Gig Performer release is written on an old Toshiba Satellite Windows laptop with an old i3 processor and 4 GB of RAM. Works flawlessly.
(even on Core2Duo! )