not sure what happened it just crashed when saving some rackspaces
can someone look at this one and tell me what happened
GP crash workign with new VST.zip (311.2 KB)
@jweisgal
Can you reproduce the crash? If yes, then I would like to work closely with you to find the root cause. The crash log doesn’t give much information unfortunately.
@jweisgal
I did additional inspection of the crash log.
(1)
I found many plugins that instantiate both VST2 and VST3 of the same plugin, E.g. Arturia, Korg, … Please make sure you use either VST3 or VST2 per plugin but not mixing both (as there were confirmed crashes to other users because of that mix).
(2)
I also suspect the usage of several instances of OP-X PRO-3, please try to disable it and check if the issue is reproduced.
(3)
I would try to upgrade to the latest version, currently you are on 5.2.2.
1 - The challenge for VST2 and VST3 - is that I bought preprogrammed NARF sounds in which he used VST2 and I have been using VST3 for mine - when you say mixing both - if you mean in the gig file its an issue -
2 - unless there is a clean way to use narf vsts and change them to vst3 ? that would be great (less plug ins) (I just started using Claude - maybe some coding here?)
OP-X PRO-3 - this is an amazing plug in with so many good sounds that I need it - is there a way to get stability?
3 - will upgrade right now
4- THANK YOU!
See this blog article
Sadly I was using VST3 to build my gig file from day 1 - then I bought NARF sounds and didnt realize he was no using VST3. Which begs the question - what’s the fastest way i can take his VSTs and recreate them in the VST3 format? And then how do I apply this through my gig file FAST.
I will back up the file and use replace plug in - is is that simple?
From the to be replaced plugin save the preset with the plugin mechanism to save a preset.
Then replace the plugin and load the previous saved preset with the plugin preset mechanism.
No! There is no guarantee that the state of a saved plugin in one format will be compatible with the expected state of another format. It might be, depends on how they implemented state save and restore but I would be very careful
This is the classic case of mixed vst types of the same plugin. Dadi, David and I had this issue with my initial setup about 2 years ago and all the crashes lead to this… Since I swapped to 1 single vst type ALL my troubles disappeared completely. Not 1 single crash since.
Thanks team
Here’s how I’m handling it — going rackspace by rackspace on the ones still using the purchased VST presets:
-
Check the format first. Hover over the plugin block — tooltip tells you VST or VST3.
-
If it’s VST, copy the name first. Grab the display name from the renaming section before doing anything else — the VST3 version usually loads with a generic default name, so you’ll want this to restore it.
-
Export the preset. Open the VST plugin’s own window, hit Export Preset, save it to your Documents folder.
-
Replace the plugin. Right-click the block → Replace Plugin → pick the VST3 version of the same instrument.
-
Rename it. Paste the name back in.
-
Import the preset. Open the VST3 instance’s own window, hit Import — the file you just exported loads right in. Surprisingly painless.
-
Verify controls and switches. Go through anything you customized beyond the base sound — bypass switches, mini-controls, whatever’s tied to song structure. Sound itself has been carrying over clean; if you built your own control layout on top of a preset, double check those still work.
So far so good — no dropouts, clean transfer each time.
My same procedure… Fairly arduous but effective
and THEN i ran CLAUDE and asked it to review stability - and it caught a few missed VSTs that were not removed and replaced.
Overall Im feeling WAY more confident on this rig - practice tomorrow night! we will see 
Thanks for the report! I might do this for my gig too, with a historic mixture of VST and VST3 for Omnisphere.
What about widgets mapped to replaced plugins? Did you have had to assign them one by one?
Well I updated Kontakt 8 last night and now I can’t get GP to open any of my gig files - its hanging and Im in practice without keys
I let it sit with the spinning wheel of death and it finally loaded. Could be the Kontakt file updating all the VSTS?
Why ?
That is a serious question. You’re in the middle of getting your current rig working without plugins with different formats are being loaded. Wouldn’t you want to make sure you’ve fixed your existing issues first before possible creating new problems with other changes.
I’m still using Kontakt 6 myself even though I have a license for the latest version. I have found Kontakt 7 and 8 to be quite buggy,
How long did it take? You might want to reset Kontakt’s cache and disable its reporting of statistics back to its mother
Actually, I’m not in the middle of updating my rig. It’s been done. I was able to get all the VST’s uniform in vst3 format (took a chunk of the weekend) I could probably remove all VSTs and Aus from the computer at this point (I have a few gig files to check)
It took 8 minutes to finally kick in
since its loading fine now and I have a gig tomorrow - im leaving the cache alone and the reporting feature was already turned off
Btw - Claude code is fantastic it was able to catch a few that I missed
Just use the plugin manager and disable plugins you don’t want to load. You could sort by format and disable every AU say (that is what I did) and you could search for Kontakt and just disable VST