Depending on how particular AU, VST3 or VST plugins needed to be activated, it may be the case that the Gig Performer’s plugin scanner was unable to validate them. There are four main reasons this might happen:
- The plugin is proprietary,
- The plugin is 32-bit,
- The plugin is corrupt,
- The plugin needs to connect to a license server but there’s no internet connection or it’s taking too long to activate,
- If you do not see the plugin at all in the Plugin Manager, it is also possible (typically on Windows computers) that the plugin was installed at a different location than expected so the plugin scanner did not find it. In this case, please follow these instructions to add the folder containing the plugin to the list of locations that need to be checked.
- If you are a Mac user and your Mac uses the new M1 processor, please check this blog article to learn more how to resolve possible problems with missing plugins.
In case 1, there’s really nothing you can do. Generally, an audio plugin host cannot access plugins that are proprietary to another audio plugin host.
In cases 2 through 4, the failed plugin with be displayed in red at the bottom of the Plugin Manager window. See this example:
Once a plugin has been deactivated, the Gig Performer’s plugin scanner will not normally attempt to validate it again.
To force Gig Performer to try to validate the plugin again, just select the failed plugin and press your backspace or delete key to remove the plugin from the list. Then perform another scan and the plugin scanner will attempt to validate it again. Note that if the plugin is not 64-bit, it will still not validate and you will need to use bridging software such as jBridge or 32-Lives to be able to use it. We do however recommend that you stick to 64-bit plugins.
The Windows build of Gig Performer v4.7 allows you to easily check the plugin architecture of a plugin. This way you can easily determine if a plugin is 32-bit. To learn more, please visit this link.
Also, for general guidance around plugin installation on Windows, see this article about best practices for managing plugins on Windows.