Hello, everyone!
I am a Gig-Performer newbie on Windows 10 and built my first over 100 rackspaces with an associated setlist.
I mainly use VSts like Analog-Lab, Halion, Kontakt7, Nexus an Halion Sonic.
Because of that I thought, it would be a good idea to insert them into the Global Rackspace and saving the needed sounds from there as favorites and to use these favorites in the individual Rackspaces.
I turned on Predictive Loading with 3 instances to minimize the loading time of each Rackspace. But I notice, that due to partially sample-intensive sound, the loading time seems very long.
Therefore I would be happy to hear your thoughts, how I could optimize my installation.
I do not understand that, when you load favorites in the local rackspace the plugins are loaded in the local rackspace.
What is the global rackspace for?
What do you want to optimize?
Cpu, RAM, loading time of a rackspace, loading time of the gig file, switching time between rackspaces?
Just as a side note: A common āmistakeā (I do not mean to be harsh) is to optimize things while youāre not having trouble. If your system can handle the 100 rackspaces well, then donāt optimize the plugins away to the Global rackspace. Youāll offer lots of handy features like, quick switching between āpresetsā (āThe rackspace is the presetā motto), patch persist, etcetera. Predictive loading only applies to common rackspaces and is there to alleviate the resource problem when you have a resource problem
Hi, pianopaul!
Thanks for your answer. Youāre right. First I thought, that using user-presets from Multi-Vsts like Halion Sonic that are placed in the Global Rackspace would save loading time, hoping that no further instance of HS needs to be loaded. But that is not true.
To be honest, the main problem of mine is the switching time between Rackspaces.
(CPU 13% / RAM 30-50% of 16GB)
You could use a combination of predictive load and set list mode.
You could build separate set lists and set predictive load to a number so that all rackspaces used in the actual set list are loaded.
This way you can seamless switch between songs in the set list and can save RAM
@ npudar, Frank1119 and David-san,
Thank you for your thoughts.
Yes, I can load 100 rackspaces into my RAM, but then memory is full. To forego predictive loading to maximally reduce loading times canāt be a solution. For me 3 rackspaces seem to be the best choice.
And yes, I would have to waive on many advantages of the rackspaces.
Can you explain this? Whatās the issue with CPU 13%, for example?
Switching should be instantaneous if all rackspaces can be loaded - otherwise, if you use predictive loading and are following a set list (or rackspace sequence in order) it should still be instantaneous.
Thereās a short ātailā of the rackspace thatās being deactivated. During that time both rackspaces are active, which might result in a short time of high(er) cpu usage.
Please excuse my late answer, but I didnāt have the time to continue working on it.
You are right, loading all rackspaces ist leading to instantaneous switching but nearly 90% of RAM-use. In the meantime I discovered, that after a while this very high ram usage is getting less, so that there is enough place for other applications that I use.
Only the loading time at the beginning is very long, but I can live with that.