Do you use multiple instances of Gig Performer?
What are your use cases?
–
Index of additional tips
[1] Automate opening instances on Windows with a BAT file (link) [2] Tips for macOS users (link) [3] Use the Task Scheduler to open instances on the Windows startup (link) [4] Learn how to sync songs in a setlist and to sync widgets across instances (link) [5] Location where instances are stored (link) [6] How to use multiple instances of Gig Performer with Jack (link) [7] Related blog: “Clever ways to optimize your plugin usage” → LINK [8] How to sync 3 instances on the same computer (link)
If you don’t like to see the command prompt window at all, you can save this code as (say) script.vbs
Set WshShell = CreateObject("WScript.Shell")
WshShell.Run chr(34) & "C:\Users\PC\Desktop\Script.bat" & Chr(34), 0
Set WshShell = Nothing
Just make sure to provide the correct path to the Script.bat file. The same applies, in some cases, you’d have to run this as administrator.
–
You can use the Task Scheduler feature in Windows to start the bat file when your computer starts or on certain criteria. See this post for more details.
Is it possible to keep two versions with different parameters in terms of cpu compilation? I would like to have one instance on desktop as intel-rosetta mode and one as M1-native.
To be sure to keep my gigs and test migration to a full M1 system
Hm… These executables for new instances on Mac are behaving like applications (they ask for permissions, etc.). Couldn’t you just in the application’s info check “Open Using Rosetta” ?
I am using intel-rosetta version. But I am planning to switch to M1 native. It could be comfortable to keep both versions ready on desktop. Just in case old gigs cannot be migrated easily…
i´ve not checked above links vs. mac.
But @rank13 has posted here a script for ARM macs that allows to open GP from your toolbar.
i have it installed. (guess the above links are related)
I can open/load 8 instances of GP4 directly !!..from toolbar.
four ( 1-4) as ARM native / four (1-4) as rosetta based.
easy peasy. Just one click into the toollbar, plus a double click, and the desired GP4 version starts.
( i have deactivated ALL these settings in global settings:
“check automaticly for new plugins at startup”, = NO.
and important for me: “load last project at startup ?” = NO
/ both caused some “issues” for me. This way its better / i´d recommend to do same )
Audio settings can remain, per individual GP4 instance, from start to start,
or i can lose these sometimes. Thats the only thing i need to have an eye on it.
Right now, i´ve longer not lost any Audio settings.
end fazit: GREAT !..works all like a charm !
just chose a good naming sheme for these GP4 instances in the script. it helps
in short: —> to have choices !
4 instances in direct reach !
BUT: i wanted to have the ARM native available as well.
TL;dr:
so far, i could not switch over to run GP4 ARM native.
just for some small tasks
( i don´t need to load 8 instances at the same time ! I probably never loaded more than 3 instances at the same time )
another reason “was”:
the hope that dependend on which GP4 instance i would use,
ït would load with the last Gig used.
This was working partially , and partially did not worked out.
So, i finally switched over to deactivate “autoload” on all instances for a more consistent workflow. Most often i would get to see the last used GIgs in the load dialog vs. different GP instances.
Another reason vs. choices: the audio interface settings per GP instance.
Here same: sometimes it kept settings, and sometimes not.
( Finally, all a thing of finding my personal best workflow, working within a computer )
OK, cool
I linked this thread in the blog article, so I assume that readers will be interested in reading all use cases that our fellow community members use.
Tried everything on task scheduler and could not get it to work,
I placed script in start up folder and works.
I would really like to have task scheduler working though.
Cheers
I (we) just started using a second instance of GP4! I think the main motivation was to reduce the load time for our drummer’s gigfile, which was getting cluttered up since I’ve been adding more synth plugins. Instances of Pigments, in particular, take longer to load. So I copied the song rackspaces that use synth plugins (I’m up to 6 now, using Reaktor, Kontakt and Pigments to augment or replace my Nord Modular G2X sounds) into my own personal GP4 instance. Now the drummer’s gigfile, with its 40 song rackspaces, loads nice and quickly, and my continuing expansion into virtual synths won’t affect him.
The other motivation was that the drums were starting to have occasional dropouts, distortion and note pile-ups at gigs, and it was back to the drawing board to find and disable more macOS processes that could be getting in the way of real-time performance (and I’ve since upgraded to Big Sur, see [blog] Optimize your Mac for a gig - #13 by therealgps). Having a separate drummer’s instance of GP4 makes it easier and faster to quit and restart his gigfile.
I set up the Mac Script to load both instances, and also exported all settings in each instance so I can easily import them when switching to the audio interface we use on stage. This is all great stuff, thank you Deskew!
