Is there a way to start a dedicated GP Instance with a given GIG file from command line in Windows?
E.g. via GP command line arguments? A known command line argument to start an
instance is “-in=” but this does not allow for providing a path to a gig file as ususal when no “-in” option is used.
Or is there any option to start the instance with empty gig and then later open the given gig file per scriping? I hav’nt found any in the documentation.
Background is: I want to open GP with multiple instances and distribute my Rackspaces across multiple GP instances to leverage the CPU power of multiple CPU cores (up to six on my laptop). I tried this by interactively opening the instances and gig files with respective portions of an original, complete Rackspace setup. This allowed me to significantly reduce the possible ASIO buffer size without causing any clicks and pops, even with multiple processor-intensive VSTIs. Now I want to do this by an automated/scripted startup of all instances and GIG files (Batch Files, GP Scripting).
If you start instances with the -in=[name] option each instance will automatically load whatever the last gig was that the instance by that name had loaded before.
You should be able to start a few named instances from a batch file and the load the gigfile you want for each of them. Next time you run the batch file they should each load the correct gig.
But I want to start let’s say 3 instances each of them loading a dedicated different gig containing only one rackspace containing only one VSTI (e.g. 1. instance with Keycape C7 Grandpinano, 2. instance Keyscape LA Custom and 3. instance with VB3) and finally the main instance containing my complete setlist of rackspaces, each containing only the remaining VSTIs for the given song but linked to the VSTIs in the other instances if needed.
But unfortunately the “last gig file” to be loaded automatically on next startup is no stored individually in each of the Instances but globally and shared by all GP instances. So the next instance on startup just loads the gig which has been loaded most recently by any other instance or even the main instance. So unfortunately I cannot map the instances 1:1 to their dedicated gig files.
I have to add that I still use GP4. Could be this is enhanced in GP5?
I think a good solution would be, to enable specifing a gig file by command line argument, even if an Instance name is specified too in order to load a given gig in a given instance.
In GP 5 each instance (if you start them with the option -in=guitar for example) has its own set of preferences and will remember what gigfile was last used in that instance. I believe the specific settings files they pull are in C:/Users/[username]/AppData/Roaming/GigPerformer/GigPerformer.[instancename].
I use this every day on multiple computers. I have different desktop shortcuts to start a keyboard instance, a guitar instance, and a drum instance. They each remember whatever gigfile I ran last in that instance.
I’m pretty sure I was doing it this way in GP 4 as well.
first I’d like to clarify that I’m both “MarkSlowhand” and “Markus”. After a longer absence, I’ve forgotten my old account “Markus” and re-registered here as “MarkSlowhand.” So please excuse me writing here using both names, probably causing some confusion. I will finish this thread as I opened it as “MarkSlowhand” but then outside this thread I will continue with my old Markus account.
An now back to the initial question. After your very helpful comments I tested my scripts for starting a number of instances by “-in=…” option with “reload last git on startup” option enabled and I found the reason, why the “last gig” seems to be stored globally across all instances and not sepaerately 1:1 for each instance.
with double quotes aroung the -in=I2 option which obviousy caused GP to not recognise this option and lets him start like the normal main instance. After removing the double quotes it now works pretty well!
