[blog] How to find out which plugin crashed Gig Performer

[npudar]

Developers of IK ToneX Amp fixed crash in their plugin in version 1.0.2.

More info here.

–

Helix Native VST3 fixed their crash in v3.51 → LINK

[npudar]

A new version of OP-X PRO II was released and devs fixed the problem → LINK

OP-X PRO III → LINK

[npudar]

The Nexus 4 team fixed the crash in the latest plugin update (as of time of writing v4.5.5).

LINK

[npudar]

I had issues with GP crashing on my M1 MacBook Pro, and per crash logs it appeared to be Omnisphere. I reached out and provided them all the info, and they verified that it was an issue with Omnisphere. Two days later I had a patched version to test, and it appears to have resolved the issue. Assuming the fix would be included in an upcoming update.

(source)

[npudar]

Kontakt glitches and crashes

• v7.6.1 - Intermittent CPU spikes on macOS (link1, link2)
• v7.7 - Sometimes when you load a Multi via the recent menu → crash (link)
• v7 - rackspaces with Kontakt 7 with 3 or more stereo outputs from Kontakt - crash every time!!! → link

[npudar]

Feedback from Synthology Ivory developer:

We have an updated version of Ivory 3 for Windows that has fixed some crashing problems.

This update is v3.0.3.2
The crash was detected on Windows computers and the developer promptly fixed the crash in this plugin.

<ExceptionAddress>0x255d2e1ab3f</ExceptionAddress>
<ExceptionModule>C:\Program Files\Common Files\VST3\Ivory.vst3\Contents\x86_64-win\Ivory.vst3</ExceptionModule>
<ExceptionModuleBase>0x255d2980000</ExceptionModuleBase>
<ExceptionModuleVersion>3.0.2.0</ExceptionModuleVersion>

[npudar]

The version 2.0.2 of the Zenology in the VST3 format may crash on save on Windows.
Quick solution: replace it with an older version.
(it is confirmed that an older version doesn’t have this bug).

Link: Crash on Save - #9 by kbmatson

[npudar]

Spectrasonics Omnisphere

---

A) GUI

@gregosophy

That GUI issue is caused by going back and forth between AU and VST versions of Omnisphere within the same project.

(source)

–

B) Crash

@gregosophy

I have been having a problem in GP that when I change Omnisphere presets, GP would crash constantly. I sent in a crash report and GP tech immediately narrowed it down to Omnisphere. This is crashing inside Omnisphere when Gig Performer is loading the plugin. It seems to want to load a sound bank (FXBFile) and the crash is occurring inside Omnisphere during that process.

Spectrasonics knows about this problem and sent me an Omnisphere install fix which will be released soon as a general update.

(source)

[npudar]

Bug in Sample Tank → LINK

–

A side note:

As a general rule, when it comes to plugin crashes, you should always make sure you’re using the latest version of the plugin before reporting an issue.

Explanation: it’s not worth trying to debug a system with out if date plugins as the issue causing the crash might have already been addressed by the plugin developers.

[npudar]

Pneuma Pro has been updated to v1.1.2

The bug with Gig Performer’s MIDI File Player has been fixed.

–

ReMIDI - the latest version of the plugin is fixed → LINK

[npudar]

DiBiQuadro - All plugins update + Resizable GUI

On macOS we have ready also the fix for Wavelab and Gig Performer. There will be another release soon for our plugins.
Unfortunately we are forced to test each DAW one by one. Contrary to Windows, for which the resizable GUI works the same way for every DAW we tried, on macOS there are at least 3 standards to resize in the host. This is pretty annoying for us!

(source)

[npudar]

Per user reports, Arturia fixed the crash in the plugin Arturia JP-8 V in the version 4.6.0.4395.

–

A word from the founder:

@dhj

Six years ago when we had much older versions of Gig Performer, I wouldn’t have been as quick to suggest the plugin but these days, Gig Performer is solid enough (thank goodness) that such crashes are generally due to the plugin. Based on the report and the stack trace, my bet would be that the plugin tried to directly perform a GUI operation from the MIDI thread. While that will work occasionally, it’s a time bomb waiting to happen, totally depending on what else is going on at the time.

[npudar]

AJlabs’ VProm Linndrum VST3

–

AJ from AJlabs has confirmed that the VST3 version crashes, because this version was compiled with an older SDK. The upcoming VProm3 will have the latest version of VST3.

In the meantime VST2 works and is solid.

(source)