02 Feb Advanced
The advanced options dialog is used to enable some of Gig Performer’s more sophisticated and unique features.
“Multi instance support” allows you to run more than one instance of Gig Performer with each instance being completely independent. If you are a keyboard player, you will normally configure individual rackspaces with all the plugins you need for each song (or song part) and all your keyboards will be connected to those plugins using MIDI In blocks. If you change your sounds a lot from one song to another, this is exactly the right way to do things. But suppose you want to dedicate one of your keyboards, such as an 88-note weighted controller, so that it’s always a grand piano. You could include a grand piano plugin in every rackspace and connect it to theMIDI In block corresponding to that controller. That’s a perfectly fine way to do things. However, you could alternatively create a new Gig Performer instance with just a single rackspace containing the grand piano plugin and the appropriate MIDI In block. Now you don’t have to include the plugin in every single rackspace any more. This can simplify your main design as well.
Another great reason to use multiple instances is if you want to process your vocals separately. You probably only need a couple of rackspaces to manage all your vocal sounds so if those rackspaces live in a separate instance, you don’t have to create them in every single rackspace of your main gig.
Another great reason for multiple instances is to allow different band members to run their own Gig Performer instances on the same computer, assuming you have sufficient CPU and RAM available. Note that with the exception of Audio In/Out, these instances are truly independent. Each musician could have a separate pedalboard to control their individual instances.
Once you enable this option – you will have a new set of Main “File” menu items where you can create, reopen or delete existing instances.
Predictive loading is an advanced Gig Performer feature that allows you to load only the rackspaces that you need in the immediate future (e.g. while playing the current song). Other rackspaces are not loaded and will therefore not consume any memory. You may also see some reduced overall CPU utilization.
This feature is useful if you are experiencing issues with memory.
The “Max loaded rackspaces” option can be adjusted to load more or less rackspaces around your currently selected rackspace. If you select 5 (default) a current rackspace as well as the next two and previous two rackspaces will also be loaded and instantly usable. Optimal use of this feature assumes you will be moving from your current rackspace to rackspaces that are close to it (within two, if 5 is the default range). As you move to a new rackspace, Gig Performer will then load and unload other rackspaces so that there are always 2 available before and after where you are. This happens in the background and does not affect your audio.
Who should use this option?
You should enable this option only if you are having issues with high memory usage and only if your rackspaces are configured in such a way that you never have to “jump” to another rackspace that is farther away that the specified number of loaded rackspaces.
What are the benefits?
The main benefit is you could load many hundreds of rackspaces and still not consume very much RAM or CPU.
What are the drawbacks?
If you use Gig Performer as a set of “sounds” rather than songs so that you are switching constantly between the rackspaces – this option is most likely not for you. While we have tested this feature extensively – it is always possible that there is a plugin out there that does not “like” being loaded/unloaded too often and so may crash. While this highlights a bug in the plugin rather than in Gig Performer, you’re not going to care if you’re on stage when it happens!
It is important that you test this feature extensively using your gig files before using Predictive Loading in a live situation to make sure it is stable for the plugins you want to use.