Converting 32-bit plug-ins (Mac)

  • Live Versions: 8.4 - 9
  • Operating System: OSX

If you run Live in 64-bit, 32-bit plug-ins will not show up in Live's browser - and vice versa. In general, we recommend to run Live in 64-bit and to install native 64-bit versions of the plug-ins where available. For any older, legacy plug-ins which are only available in 32-bit mode, it's possible to use third-party tools such as jBridge (VST only) and 32 Lives (AU and VST) to bridge them for use in the 64-bit version of Live.

Please find below instructions on how to use jBridge and 32 Lives for your plug-ins.
For detailed information on how to use VST and AU plug-ins, check out our recommendations on using plug-ins in Live.

jBridgeM

Download and install jBridgeM. Please note that jBridgeM is not freeware. You will have to pay a small fee once the demo has expired.

Performing plug-in bridging
Bridging needs to be done as a specific task before the plug-ins can be used. The process is also walked through in the detailed jBridgeM setup description:

  1. Run the jBridgerM tool.
  2. In the window that is shown, the default setting "Bridge 32bit plugins" works well in most situations. If you only have a few VSTs and already know which of them are 32-bit and need to be bridged, you can select the option to choose some plug-ins only manually.
  3. In the same window, now choose that you'll be using a 64-bit VST host.
  4. After you've done this, the jBridgerM will start analyzing all VST plug-ins in your two system folders.
  5. When this is finished, the jBridgerM tool will create a folder that contains all bridged plug-ins, as shown at the bottom of the window: /Users/[your_user_name]/Library/Audio/Plug-Ins/VST/PluginsBridgedFor64BitVSTHosts
  6. Remember this path and quit jBridgerM.

Cleaning up
If you have manually chosen specific plug-ins only to be bridged, as mentioned above, you can skip this and proceed with making Live aware of the bridged plug-ins.

Otherwise, as the bridging process has scanned all available 32-bit plug-ins, you'll most likely see bridged versions of VST plug-ins that are also available as native 64-bit plug-ins. Since the bridged versions are unnecessary here, follow these steps to remove them:

  • Navigate to the folder
    /Users/[your_user_name]/Library/Audio/Plug-Ins/VST/PluginsBridgedFor64BitVSTHosts
  • Manually delete all .vst files from this folder that you know are installed as native 64-bit plug-ins.

Making Live aware of the bridged plug-ins
Finally, to make the bridged plug-ins appear in Live's Plug-In-Device browser:

  • Start Live, open the Preferences and show the File/Folder tab.
  • Make sure "Use VST Plug-In System Folders" is enabled. Alternatively, you can enable "Use VST Plug-In Custom Folder" and select /Users/[your_user_name]/Library/Audio/Plug-Ins/VST/PluginsBridgedFor64BitVSTHosts as the Custom Folder.
  • Live will now scan this folder and show all bridged VST plug-ins in a dedicated subfolder in the Plug-Ins Category in the Browser (Live 9) or in the Plug-In Device Browser (Live 8.4).

Updates of Live
Updates to Live will not affect this functionality, so your jBridgeM settings and bridged plug-ins will still work after updating. Updates to jBridgeM should be installed over the older version.

Troubleshooting jBridgeM issues
Should you encounter issues with jBridge, please refer to general troubleshooting tips. Please note that running jBridgeM on later OS versions (10.9 and above), requires further adjustments as explained here.

32 Lives

In case you use Audio Unit plug-ins, you may want to try 32 Lives by Soundraxis. Please note that 32 Lives is not freeware and requires a purchase of a license.

For detailed information about the installation, authorization and the actual plug-in bridging, have a look at the 32 Live user manual.