In setlist mode you can use the Shift key to rearrange songs without activating them.
I have a setlist with all our songs (40) and when I prepare for a show I put the songs we play in order on top (around 20) and leave the rest at the bottom of the list.
That way you can use predictive loading to speed up the startup time and during the set shift-grab a song and put it at the right spot in your list?
I don’t use predictive loading since a few minutes startup time does not bother me and I use multiple instances so that also shortens the time needed to startup (I can open a New instance while another is loading)
At some point I suggested a “quick load option”, which is sort of a hybrid of Predictive Loading and a (standard) full Gig File load. The idea is that it would initially (quickly) load a certain amount of songs/rackspaces (let’s say your first set at a gig). Then, possibly while you are playing the first few songs of the set, it would load the rest of the gig file.
Once the full Gig File was loaded, it would cease operating like Predictive Loading. (There would be no need, as all the songs/rackspaces in the Gig File are loaded).
That way you can get up an running to start your gig quickly, but once it is loaded you get the full access to the Gig File (and potentially greater stability) of the “regular” load in of the Gig File.
It would be a nice option for people concerned about load time, but who have enough ram to load a full Gig File.
Well, to be honest… I really appreciate GP’s rock solid stability right now.
So instead of trying to change the way it’s designed to be used, I rather find my way to deal with a bit longer startup time.
Actually I purchased a UPS (uninterrupted power supply) to be able to connect my hardware and load my gigfile backstage on a rolling riser before I’m plugged into the main backline power.
My big Gig File takes a bit of time to load (not quite 10 minutes for the full Gig File).
But, it generally is not a big deal. I just leave part of my set up to finish for those 10 minutes. So, when I am done with that part of my set up, everything is fully loaded. (Luckily, others handle the PA).
Mostly just the few second wait while plugins load during song switches. None of my plugins call home on startup but I know there are plenty that do and it would be ideal to have those loaded before the gig starts.
I like this idea too. Seems like there are a lot of options for faster startup.
The way I run my system is I basically have a rack space for each song (one or two songs have two rack space files to load).
If your songs are set up and saved individually like that, you can have a file folder of your saved individual rack spaces open in the background, and drag and drop into GigPerformer from there when you determine what new songs you are going to play. Loading should be relatively quick.
You of course would have to have a monitor and mouse near (which I do).
Just another option to think about.
I’m usually setting up and powering on my analog synths OFF stage to allow them to acclimate temperature-wise at least 30 minutes before my set. You could do the same, especially if you’re having to wear many hats regarding helping out with PA needs, etc. This is also why one of my major stress dreams is getting to the gig when we’re supposed to be on stage already, and having to throw everything up there and set up while the clock is running!
I can relate to the issue – I have a large gig file for my main band, currently with around 40 rackspaces by now (and counting). I’ve tried using predictive loading, but it does not work well because the setlist rarely uses consecutive rackspaces. I also experimented with exporting setlists to separate gig files, but the problem is that during a live performance, there’s always the chance we’ll play an ad hoc song at the end, which would require loading the full gig file in the middle of the show.
An option to load only the rackspaces used in a setlist could be helpful in that scenario, specially when dealing with large gig files. The behavior could be: load only the rackspaces included in the current setlist; if the user adds another song, load only the additional rackspaces needed. If the user opens the rackspaces screen and clicks on individual rackspaces, load only the selected ones.
This could be a way to reduce resource usage for bands with large repertoires, as it caters to the most common scenario in live performances: things start with a planned setlist, but it can always have last-minute requests or changes. Right now, I still have the luxury of keeping all my 40+ rackspaces ready to go - but what happens when that number keeps growing?
But, I think you can already do this. Just use Predictive Loading in Setlist mode and set it to the largest number of songs you can (up to the full set list). Then it should load all those songs/rackspaces. If you go outside those songs, it may take some time to load. (That’s my understanding, anyway).
If you are in several different bands, another option is to create a gig file from the setlist and including all songs that particular band does.
If course, getting more ram is nice if its an option (I know, duh!). I think it is easier (or at least less expensive) to get lots of ram with Windows computers now than Apple. In my Lenovo Thinkpad P.16 (Gen. 2) I have 128 GB ram (I believe it could go up to 192GB).
I think I have maybe 150 rackspaces in my big gig file (?).
Hi, what I do is having all my 80s songs in ableton Live, organised, adjusted and programmed as a nice setlist, then, send the audio and midi to GP through gprelayer (both programs work together like a charm); in GP I have all the rackspaces for each song and the plugins. With just a hit on a key on my laptop every sequence starts immediatly, no hassle, no waiting. All my keyboards and guitar presets are ready to sound exactly as I want them to be, for every song.
I have 550 in mine. With predictive set to 1, my Surface Pro 9 (12gen/32gig ram) loads the entire gigfile in 4:03. I’m happy with that. Individual rackspaces load in 2 or 3 seconds, or up to 10 /11 seconds depending on the number of vsts in the RS. I don’t use set list mode, I think the developers have done a grand job with loading of racksp[aces.
