Projects using the EZbass VST 3 plug-in saved on Windows cannot be loaded on macOS and vice versa due to how the identifier for the VST 3 plug-in is reported by EZbass, and this bug can unfortunately not be fixed without ruining old projects on one platform. We have, however, introduced a toggle in the advanced settings that allows you to work around this issue in EZbass version 1.2.0 and onwards.
This workaround can cause other problems:
Unaffected hosts and plug-in formats
If you are trying to load a project with any of following hosts and/or plug-in formats, you shouldn’t use this workaround at all. Loading the EZbass plug-in should work and there is something else causing the issue if you can’t load the plug-in.
Solution:
Insert a new EZbass plug-in in the project, then navigate to Settings > Advanced in the plug-in and select the ID option that matches the OS that the project was initially saved on.
Depending on the situation you are in, it is important that you select the correct option. Click the buttons below to reveal when the different options should be used.
After making sure that the DAW knows that the plug-in ID has changed, you can load the project.
After selecting the correct ID, you may need to do more than just restart the DAW to update its plug-in database so that it knows that the plug-in ID changed. Select your host below for more information.
Ableton doesn’t know that the plug-in ID has changed at this stage. Follow the steps below to force Ableton to rescan the new ID.
Please do not use the toggle if you are on Cubase version 12.0.52 or above. In that case, Cubase should be able to load the EZbass.vst3 even if the project was saved in Cubase on another OS.
Cubase doesn’t know that the plug-in ID has changed at this stage. Follow the steps below to force Cubase to rescan the new ID.
Digital Performer doesn’t know that the plug-in ID has changed at this stage. Follow the steps below to force Digital Performer to rescan the new ID.
Delete the “VST3 Info Cache v2” file in that folder.
Delete the “VST3 Info Cache v2” file in that folder.
After selecting the correct plug-in ID option, restart FL Studio and you should be able to load EZbass in the project that was saved on the other platform.
After selecting the correct plug-in ID option, restart REAPER and you should be able to load EZbass in the project that was saved on the other platform.
After selecting the correct plug-in ID option, restart Reason and you should be able to load EZbass in the project that was saved on the other platform.
Studio One doesn’t know that the plug-in ID has changed at this stage. Follow the steps below to force Studio One to rescan the new ID.
In the versions we’ve tested, this workaround has not been needed to load the EZbass VST 3 plug-in even if it was saved on a different OS/platform. But just in case it is needed in your version:
If you are having issues updating the plug-in ID in your DAW and the plug-in just won’t load anymore even in new projects, you can always open the standalone application and go back to the ID that was being used by default.