The latest blog article: Don't mix plugin formats from the same company - Gig Performer®
This blog article is great for getting insights on how the path of troubleshooting issues goes.
Kudos for our developers!!! 
10 Likes
That was quite a find! 
Greatly appreciate these guys pushing the issue through to a resolution. I had similar problems with a competing product after I allowed NI to update my libraries. My lesson learned was never allow any updates to OS, VSTs or anything else unless I have a few weeks to the next gig to resolve any problems it may cause.
It’s a shame NI has those compatibility issues. The older versions sometimes have different timbre from the newer ones in many cases and sometimes you just want to stick with the older one while other times you want the newer one.
While I still exclusively use NI, I feel compelled to start from scratch, rebuilding all my older rackspaces when I allow NI to update. It’s not that they don’t work after the upgrade. It’s that when I add new songs, I sometimes end up with exactly the problem described in this blog - at least on the competitors software. I haven’t seen many crashes with GP. But I am also very update averse since moving to GP.
What crashes have you seen and were they GP crashes or plugin crashes that brought down GP?
I haven’t seen any crashes during performance or rehearsal. And I’m not even sure I have seen any in GP5. I know I had some in GP4. The band I play with is constantly changing directions which sometimes results in me having to make lots of ridiculous changes to my gig file. That is when I have see 3 or 4 crashes. But I haven’t even seen one of those in quite some time now. So I’m not concerned yet.
My biggest problem with performance failures has been Win11 and all of the tentacles Microsoft and Dell have in the OS that can cause issues with a real time item like GP. I don’t seem to have near the problems with my Win10 backup machine. last gig, it stopped sending sound to my IO for about 15 seconds. I think I finally found the last of those little gremlins though. Microsoft seem to think they own the computer even though I paid for it. 
That is exactly what we have been recommending for years! 
–
If you do experience a crash, you can always post the crash report here, in the community. We encouraged people to do so in our newsletter. The crash report doesn’t lie!
–
If you took care of all your gremlins, make sure to share those tips with us
It will be beneficial for other Gig Performer (or any other software) users.
Thanks for sharing these insights!
Learned something new again
And, indeed, I found something in one of my gig-files: a mix of Blue 3 VST3 and AU version
Fortunately without consequences - so far…
BBB
I have read in the blog article that you have reached out to Native Instruments. Maybe you could do the same thing with UVI, because Falcon makes Gig Perfomer crashing almost every day on my system. I have reported that already in a different post in this forum.
You should forward the crash report to UVI.
This was recommended on several other places (example).
The logic is, more of you folks beat the developer, it is more likely that they fix the bugs.
Did you report it to UVI?
In general, it does not make sense for us to be the interface to every plugin developer for every possible bug in an arbitrary plugin - once it becomes clear that the bug is in a plugin and not in GP (basically a crash report that proves this), then the customer should report it to the developer. The crash is going to happen to many users. There is nothing we can do about such issues.
Developers can reach out to us if they need more information but 99.9% of the time, they are going to be able to use that crash report to hone in on the problem immediately.
The issue we described in this blog article was extremely unusual (which is why we thought it would be interesting to write about it). For a start, as mentioned in the article, we had no idea what was causing the problem, there was no useful crash report. It was not reproducible and was happening at random. And all we could see was that it was GP that was terminating and so we could not rule out an issue with GP itself. That is why we had to eventually reach out to NI when we determined that their plugins might be contributing to the problem — remember that many people (including us) use NI plugins as a staple without any issue.
The solution was still something that had to be done by the customer, not by NI. That is not the case for the UVI issue that you mentioned.
Also, the solution, which we now suggest as a best practice, applies to plugins from other developers as well, so it’s much more general, which is another reason we wrote this up.
5 Likes
I have reported it a moment ago to UVI. Vamos a ver que pasa 
2 Likes
Me, the culprit!
I just want to say publicly :
Thanks a million to David, Eldad and anyone else implicated in this adventure… It was a bit of a bumpy ride but as it says in the article, I wasn’t willing to give up… WE weren’t willing to give up.
I’ve fallen so in love with GP and can only speak wonders about it, the developers and the community… Getting word out there slowly
Cheers
M
8 Likes
I’m concerned about sharing some of the changes I made. My laptop would now be very vulnerable if connected to the internet. Because I use it as a dedicated and non-connected machine and have managed to avoid malware for several decades without Microsoft’s assistance, I am comfortable with these changes. But I dare not recommend those changes to others that may not be as careful as I am. Wouldn’t that make me culpable if their machine falls victim to malware?
It may work for somebody else who is not connected to the Internet.
(I haven’t been running an antivirus for decades, for example.)
1 Like
Just always put a disclaimer at the top, e.g. “This is what I do - use entirely at your own risk”, etc.
Thank you for this blog article.
Although I’m not familiar with IT development, I really appreciated the way the investigation unfolded, explaining the procedures followed, which were quite clear and understandable even for a neophyte.
This could have been the subject of a movie adaptation: a thriller called “Les Liaisons dangereuses (Dangerous Liaisons)”, but the title is already taken 
3 Likes