I have two different 61 key controllers that I use - one for a practice setup at home, and one for gigging. I have an alias setup in Rig Manager for these. Every I time I have to change the device assigned to the alias, two things happen: 1) Even though I hit Apply and Save, the dialog remains and when I hit close, another dialog pops up warning that I am leaving the previous dialog without saving my changes, and 2) since I am forced to just say okay to that dialog, GP5 then crashes. This is pretty frustrating since it is already a sizable gig file that takes 2+ minutes to complete loading. Anyone else encountering this, or have a better workaround for such a setup?
Did you try just to create 2 Rigs, each with the desired midi device learned?
You should make those rig manager changes with an empty gig file and then load the gig file after
A combination of the two responses above is working for me, thanks! I changed the preference to not load the last gig file at startup and now have individual rigs setup for each situation to select, so I can avoid the crash. (Migrating from Mainstage, so I’m still falling into traps from the differing workflows)
You actually don’t need to do that. If you have that preference enabled, and you want to just sometimes not load the last gig file, simply hold the SHIFT key down while GP is opening and you will get a dialog where you can temporarily disabled loading.
Can you post the crash report so we can see what happened?
I captured the report to a text file. It’s pretty large - about 1.3MB. Thread 0 is the one that crashed. Hopefully it’s not too large to attach…
GP5Crash.txt (1.3 MB)
Oh, and thanks for the tip about using SHIFT!
The Shift key is magical in the Gig Performer world: [blog] The Magic of the Shift key
Normally compress such things but we will take care ofnot
Are you using GP Script?
Yes, I am using scriptlets throughout many of the racks for bank/program change messages in rack variations.
What I’m seeing in that crash report is rather strange - it looks like the Apply button was pressed more than once - is that possible? The GP Scripts get recompiled automatically when you apply a new rig and it may be that there’s an issue if Apply is pressed again before the system has finished with the existing recompile
It is possible. My experience was getting no response when pressing Apply or Save and thinking that nothing had happened. I am sure that in the several instances I have encountered this, that I might have pressed Apply twice, or Apply and then Save, or other combinations. I was not aware that recompilation had been triggered - it could be that had I waited however long the recompilation takes, that I would have seen something on the dialog indicating the Apply or Save operation had been done.
Thanks for that information. We may have an idea what’s going on