This morning Cherry Audio updated the Blue3 plugin on my Windows system. Now I have a gig that keeps crashing upon loading. It looks like I am using both the VST and VST3 versions in the gig which I know is bad. It looks like the VST and VST3 are also somehow different.
I’ve sent the crash reports to the Gig Performer server. Please look at the crash and advise me how I can resolve the problem.
Version 1.0.12 (870) for VST3.
Thanks.
I uninstalled Blue3 and reinstalled it. After scanning with Gig Performer the VST version has disappeared and only the VST3 version is now listed. Strange.
With only the VST3 version apparently recognized through scanning the crashing has stopped. The gig loads and I can replace the “missing” plugin with the VST3 version.
Don’t use the old version. A lot of VST versions of plugins are disappearing these days for various reasons. And, per a blog article we wrote some time ago, there can be nasty consequences to having multiple instance of plugins but with different formats or different versions.
I think what happened is I had created a new rackspace using the old version of the VST plugin. When Blue3 updated the installer is using the same location for installing the VST and VST3 versions by default. I think that’s how it got out-of-sync with an older version of the VST in one location and the new version of VST3 in another.
I don’t know why the Cherry Audio installer is defaulting to the same location for the VST and VST3 plugins.
Anyway, completely uninstalling removed the VST (older) version and allowed the gig to load.
What a mess. Upon investigation the VST and VST3 versions are being installed in separate locations but somehow the VST location changed and was not added as a scanning location for Gig Performer. Therefore, Gig Performer still had a reference to an older VST version from a prior scan and a newer VST3 version which was picked up by its scan.
I can see that I have the same problem with a Triton VST being in two different locations.
Is there a way I can get a report of all the VSTs used by a gig and their respective file locations? I need to do some cleanup: 1) Ensure no VST and VST3 combinations of the same plugin, and, 2) The VST version is not an older version when used.
I’d go into the plugin manager and sort by plugin manufacturer. Take note of the duplicates and their version numbers, locations etc. Move the newest versions to the correct location and disable the older versions. Then you can reload your gig file and the plugins using the disabled older versions will be obvious… Then you’ll know which ones you need to switch over inside the gig.
That’s hardly a surprise – Gig Performer doesn’t know into what folder an arbitrary installer placed a plugin. To be able to do that, we would have to monitor every single folder on a computer, absolutely not a practical proposition.
I agree. I just don’t know when the location changed. At one point Cherry Audio probably picked a default shared location before changing it.