As a GP newbie, I want to be sure I do my initial setup correctly. I want to know if it is best to create a master gig file for each band I play in and pull the songs needed into a setlist file for live gigs?
The amount of ram you have and the time you need to load up your rig at a gig will be important factors.
I have one giant Gig File for all my bands (Windows with 120 GB ram (that’s a lot)). Within it I create setlists for each gig. But, the setlists also (at the end) have every song that each particular band does. The load up time is pretty long for the big Gig File (a bit under 10 minutes). So, if I am at a gig where I think things will be rushed, I create a gig file from the setlist and use that for the gig. But, because I include every song that band does in (at the end) of the setlist, I feel comfortable I can play songs outside of the particular setlist (this is not that uncommon). It is also nice to have a “definitive” ultimate big Gig File because you know that any changes you make in a song will apply wherever the songs is used (unless you want different versions of the song for different bands).
I would tend to recommend that you at least start off the same way. You can always break things down in smaller gig files.
So, I would just put everything in the same gig file for now. If you have ram issues, you could shift to creating different gig files for each band by creating a gig file from a set list. (I will do that if my Gig file becomes too big that I start running into issues).
Of course, there are a bunch of other options. People export and import songs. You could use Predictive Loading. Also, there are a bunch of strategies to tend to optimize ram (Kontakt DFD and purging samples, putting large sample-based “sounds” in the Global rackpsace or at least re-using the same plugin in the same rackspace, using physically modeled plugins over sample-based ones where available, etc.).
I am curious what other people do.
1 Like
I have individual folders for each band, and keep each song as a separate file in each band folder. We get a set list before gig date and I load only the songs needed, in order, for that specific gig. If an “audible” is called for a song, it shouldn’t take but a couple of seconds to drag that song file into the gig program to load (have a file folder open in the background of that band’s song files).
Saves ram, since I’m in like 7 bands…
Just how I’ve done it since I went to a VST and GigPerformer setup.
2 Likes
I do the same as @jeffn1 . I have maybe 80 rack panels for 70 or so songs. I arrange them differently for specific shows, but leave all the “extras” at the bottom of the .gig file.
My .gig file load time is around 4:30, but by doing this, (a) edits made to panels along the way get passed on to future sets/gig files. (b) I have all songs accessible for audibles during a show (Control + F to search/find in the current set/gig file).
I recommend starting this way. If you have a future show where you need a fast load time, create a .gig file with only the songs you need from your “master” gig file, but continue using the master/all songs file after that. FWIW.
But, you have to admit that having each song exported and ready to import is nice. But, it does require some additional ongoing prep work. Since I have a duplicate backup laptop, the upfront time/tracking everything would be even a bit more.
Thank you all for the tips. That is basically how I do it in OnSong currently. Thanks again!