AppleGigPerformerCrashReport.pdf (870.6 KB)
I have a rackspace containing instances of EAST WEST OPUS (see attached screenshot). If I delete any of the Opus instances from the rackspace, GigPerformer crashes. (Apple crash report is attached).
AppleGigPerformerCrashReport.pdf (870.6 KB)
The crash report clearly indicates that this is a fault of the plugin.
Maybe this is similar to the issue described in this post
EastWest Opus is stopping GP while loading VSTs at startup
Yes, OPUS is crashing - it doesn’t like being deleted, apparently. Please forward that crash report to East West and make sure they know EXACTLY what version of OPUS you’re using – that will let them examine where in OPUS the crash is occurring.
The time when I have crashes with Gig Performer is virtually always when or after I’ve made changes to the setup. This could be in the wiring view, when scripting, etc.
After making changes to Gig Performer’s configuration of significance, or if you experience anything unexpected, I recommend rebooting the system. You never know what garbage that plugins have left behind, or what might be rattling around in the buffers. When doing development of songs with a DAW, I might accidentally create a MIDI message feedback loop. That’s a recipe for bad results.
By starting clean, you’re emulating what will happen when setting up at a gig. You can establish your sequence for turning on your outboard gear, starting apps like Mobile Sheets, etc. Get a consistent routine.
When I do this, my system is super stable. It helps me separate development mode from performance mode.
1 Like
Please post your crash reports so we can see what’s going on
Will do. They happen rarely, but are often explainable for reasons unrelated to Gig Performer.
For instance, when developing a MIDI sequence in Logic, I disable the MIDI input to Logic, otherwise it can cause a feedback loop that pummels Gig Performer with messages. When changing MIDI channels in Logic, Logic generally automatically enables the input, causing this problem. I manually fix it, when I remember to, right away. It might not crash GP, but I might get weird results. I reboot before judging if my setup has problems or not.
Also, recently I had a problem where a MIDI cable was under stress, and the audio interface and my controllers would get disconnected and reconnected. While I could reset the audio engine and get sound again, I consider this to be a corrupted state, so I reboot to ensure that things are clean.
In the future, I’ll send any crash reports, so you can make Gig Performer more resilient, even when things happen outside of the norm.
My main point is that when I don’t have these external issues, GP is amazingly solid, days on end. 
1 Like