I have set predictive loading to 3 rackspaces but already at startup Gigperformer allocates 10 GB of memory for 50 rackspaces. When I scroll through the rackspaces I can see that Gigperformer is predicting (only 3 rackspaces are marked green, others are red) but memory consumption increases continously with every rackspace I select until Gigperformer uses the entire RAM available (32 GB) and then the performance of the whole system goes down (audio glitching etc.)
At the moment I have ~50 Rackspaces and my Gig-File is 91 MB. I use plugins mainly from Native Instruments (Kontakt, Massive, Massive X, FM8) and a Roland Cloud Plugin (D-50). CPU Usage is always under 50%.
My system is a HP ZBook Power G8, Intel Core i7-11800H, 32 GB RAM, Windows 11
I am a live keyboarder and currently switching from Korg Kronos to Gig Performer. I am very happy with all the new possibilities of gig performer but at the same I have doubts as to whether the system is stable enough. I will need ~ 200 Rackspaces in the end and I thought this should be possible with predictive loading(?)
Hi David, Gig Performer Version is 4.1.5
Basically you are right. GP is stable and itâs a great software. But the memory usage is a serious problem to me. I could upgrade to 64 GB RAM but this could even be too small if predictive loading doesnât work as expected, when I have 150+ rackspaces.
Of course I donât need 150 rackspaces for a single performance but itâs great to have the flexibility to change to any song which is not on the setlist, if needed. Coming from a hardware workstation (Korg Kronos), Iâm used to having all the songs instantly available.
Thank you @npudar for this tip concerning âpurge samplesâ in Kontakt. This helps a lot, although it still doesnât solve the fundamental problem that predictive loading doesnât work properly for me.
This type of memory problem might be a memory leak that occurs in bad code. Probably from a plug-in. You can remove rack spaces to isolate. Maybe delete half the rackspaces, test, delete half of the rack spaces in the âbad halfâ until you narrow it down. I donât think this would be from gigperformer- unless your copy of the app became corrupted. Maybe delete the app and reinstall.
I agree with @thunderfingers â one of your plugins is seriously leaking memory. My guess is that the plugin in question doesnât properly handle being reset and itâs not releasing any previous RAM it was using before reloading state.
Actually, the suspected plugin can only be Kontakt (Version 6). Sometimes I had several Kontakt instances in a single rackspace with 1-2 GB each (NI Session Horns etc.) but I only needed a few notes. Now I ran âPurge allâ everywhere and saved the gig file. Now the startup memory usage is at 4 GB and it increases only to 6 GB when I scroll through all the rackspaces (playing a few notes). So the problem seems to be solved for me now.
Unfortunately, there is no global âpurgeâ function that resets all Kontakt instances in all rackspaces.
Better you play your notes and then purge sample pool.
This way all needed samples are loaded, but only this needed.
A complete purge would cause the samples be loaded when you play the notes.
Hi pianopaul. The problem is, when I âaccidentallyâ play notes, which are not needed in the rackspace (and this will happen from time to time and then save the gigfile, I have again unnecessary samples loaded, when I select the rackspace the next time.
Actually, I want my samples to be loaded when I play the notes. I have testet this - it is fast enough. When I for instance purge all samples of the piano sample âGrandeurâ (~ 1.2 GB) and then start playing, there is no latency noticeable.
I am In the process of evaluating gig performer and trial mode on a new M2 based MacBook Pro 16 inch with 16 GB of RAM and my main applications for Live use will be spectrasonics omnispere, keyscape and Native Instruments Komplete 14 and also arturia V collection 9.
I need a platform that can scale to cover >500 songs, and when running a basic racksoace with 4 omnispere instances, 1 keyscape, and 1 Kontact 7 with 1 instrument, i maxed out the ram with less than 50 duplicated rackspaces, so then turned on predictive loading, and it did slightly improve but still was over 12gb ram of my 16gb total. I then created a sample song with 3 song parts, and duplicated it 50 times, which is not even close to wharvI need to cover as a full,song list, and I was over 14gb ram.
My next test will be to create variations vs rackspaces, and then apply variations to the song parts And see if that helps.
I am a long time user of Main stage and found that the performance and scale ability to handle a large repertoire of songs was not capable and thatâs why I decided to take a deeper look at Gig Performer.
I have a studio with a large investment in virtual instruments that I thought would be great to incorporate into my live rig, which is based around a new Nord stage 4, but now I am thinking I should just create all the song patches on the Nord and use program changes from an application like on song with my iPad and completely forget about using a laptop on stage. If Iâm going to run into issues with maxing out ram and I canât budget spending more money on a 32 GB MacBook Pro that would cost me at least another seven or $800.
Interested in some comments from some other full-time professional keyboard players, that are more advanced and knowledgable with their application of gig performer, because I do like the interface flexibility and the ease of creating rack spaces
Check that none of your Kontakt instances has multiple instruments loaded in the same instance.
In other samplers, I think if you load in an instrument, it replaces the prior one.
In Kontakt, I have loaded other instruments, thinking they were replacing the prior instrument, but Kontatk just loads them also (I think to another midi channel).
One time I was wondering why my rackspace with Kontakt was using so much resources. I started poking around and noticed that if I scrolled down Kontakt, I had multiple Kontakt instruments loaded (they were all organs, so that is why I did not notice right away from the sound).
Iâm using a Surface Pro 8 with 16 gig ram and predictive set to 3. I have a âsuperâ gigfile of 450 songs. The gigfile takes 4 1/2 minutes to load, and a rs takes perhaps 7 or 8 seconds. But it all works:)
and then save the gigfile, I have again unnecessary samples loaded, when I select the rackspace the next time.