Vst Plugins 32 Or 64 Bit

Yet another developer i talked to stated that both things (64-bit plug-ins and 64-bit engine) were basically the same thing and 32-bit mix engine could be dropped because Cubase only works with 64-bit plug-ins anyway. That's why i started this topic in the first place. I personally use a lot of plug-ins that Cubase rate as being full 64-bit.

  1. Windows Vista / 7 / 8 / 10 (32-bit or 64-bit) VST / VST3 / AAX compatible host (32-bit or 64-bit) Intel/AMD processor with SSE2 support; Always use 32-bit plugins in 32-bit hosts, or 64-bit plugins in 64-bit hosts! 64-bit plugins can’t work in 32-bit hosts even if the operating system is 64-bit. Do NOT use 32-bit plugins in 64-bit hosts.
  2. 32 LIVES is a transparent 32-bit to 64-bit Audio Units and VST plug-ins adapter which enables you to run your favorite 32-bit-only plug-ins, such as Vanguard, VB3 and TC PowerCore plug-ins, in your latest 64-bit DAW.
  3. Cubase, for example. I was fine until the update when it suddenly removed totally support for 32 bit ones, and my old projects were full of them. I did manage to get the critical ones running on a bridge application, but since then everything I buy or download is 64. I just avoid 32 totally. Installing a 32 bit application is time limited.
  4. Cantabile supports both 32 and 64 bit audio as a global option - see Options - Audio Engine - Double precision (64-bit) audio. Note that not all plugins support 64-bit audio - check the plugin's documentation.
  5. If you have a 64-bit operating system, the ideal situation is to run a 64-bit DAW with 64-bit plugins. I don't know how this stuff works on Mac but on Windows, the operating system has to do a lot of extra work under the hood to be able to run 32-bit apps.

  1. We're currently conducting systematic tests with the release version of macOS 11 (Big Sur) in order to offer full compatibility of our products as soon as possible. You can find our latest compatibility status - here


    Please note that although announced at the same time as macOS Big Sur, Apple Silicon processors are an independent release with separate compatibility concerns for NI products. Compatibility with macOS Big Sur will not yet ensure compatibility with Apple Silicon processors. Free vst audacity for vocals. At the moment, Native Instruments products are not supported on computers with Apple Silicon processors. Read more - here

    Dismiss Notice

Discussion in 'Computer Technology and Setup' started by Megatron, May 26, 2020.

It's no secret that the third-party tool jBridge is a popular way to load 32-bit VST plugins in the 64-bit Windows version of Ableton Live- but all of the tutorials I've seen so far (including the one Ableton published) leave out some important steps when describing how to set things up. What follows is what I like to consider the ultimate guide to getting jBridge working with Ableton Live.
Please note that while this post is specifically about Windows, there is a Mac OS version of jBridge, called jBridgeM. (There's also a Mac OS bridging solution for 32-bit AU plugins, called 32 Lives.)
These steps should work the same for both version 8 and 9 of Ableton Live Intro, Standard, and Suite. But before we get started, let's have a quick talk about plugins.

YOU GOTTA KEEP 'EM SEPARATED

Most music folks running 64-bit Windows keep their 32-bit and 64-bit plugins in separate folders, and for good reason: Not only are 64-bit and 32-bit binaries not compatible with one another without special bridging logic, but even in the case of DAWs that have built-in bridging support (like Cubase), if your DAW detects two plugin files with the same plugin ID (even if they have different filenames- for example, ValhallaRoom.dll and ValhallaRoom_x64.dll), that can confuse your DAW and result in unexpected behavior. In general it's best to keep the different types of plugins in different directories, and to make sure your 64-bit DAWs and plugin hosts don't search in your 32-bit plugin directories, and vice versa.
What we're going to do with jBridge is create 64-bit 'wrappers' for each of the 32-bit plugins we wish to use in 64-bit Live, and the easiest way to do this is to start with a single directory that only contains the plugins we're planning to bridge.
I keep all of my VST 2.x plugins in these two directories on my DAW PC:
  • g:vstplugins32
  • g:vstplugins64
And I created a subfolder where I keep all of the 32-bit plugins that I want to wrap with jBridge:
  • g:vstplugins32plugins_to_bridge

Vst plugins 32 or 64 bitsLikewise, I have another subfolder where I keep the 64-bit jBridge wrappers for those plugins:
  • g:vstplugins64bridged_plugins

You will minimize confusion and potential problems by following a similar scheme.

ONE-TIME SETUP STEPS

Before you can successfully bridge and use your 32-bit plugins in 64-bit Live, you need to perform some one-time configuration steps for both jBridge and Live. This is generally covered at the official How to use jBridge walkthrough, but I've customized these instructions for Live.
  1. If you haven't done so already, install jBridge on your PC. While you will need a licensed version in order to get the most from your bridged plugins, the free demo version will work fine for the purposes of this tutorial.
  2. Locate the folder where you installed jBridge, and perform the following step for auxhost.exe, auxhost64.exe, and jBridger.exe: Right-click the program and click Properties. On the Compatibility tab, check Run this program as an administrator, and then click OK.
  3. Locate the folder where your copy of 64-bit Ableteton Live is installed. I installed Live under g:programs64Ableton, but if you didn't pick a custom location when you installed Live, it's probably somewhere inside your hidden ProgramData folder. Once you find it, right-click your Ableton Live executable and click Properties. On the Compatibility tab, check Run this program as an administrator, and then click OK.

BRIDGING YOUR 32-BIT PLUGINS

Before you continue, I strongly advise making sure that you have the 32-bit plugins you wish to bridge in their own subdirectory under your 32-bit VstPlugins folder, and that you create a new subdirectory inside your main 64-bit VstPlugins folder for the jBridge wrappers. Please see the 'Keep 'em Separated' section of this post for an example.
Also, make sure you've completed the 'One-time Setup Steps' mentioned above.Vst Plugins 32 Or 64 Bit
  1. Launch jBridger.exe. If you see a User Account Control dialog, just click Yes.
  2. On the first jBridger screen, click I'll be using a x64 (64-bit) host.
  3. On the next screen make sure that the following options are checked:
    • Thorough file analysis
    • Create bridging files for 32 bit plugins
    • Don't add .32./.64. in filenames in destination folder (This one's important!)
    • Optional: If the 32-bit plugin directory you're going to specify in the next step contains plugins that you don't want to bridge, check Confirm each file individually. This will display a Yes/No dialog for each plugin jBridger detects, letting you choose which plugins to create wrappers for. If you don't do this, you'll have to manually delete any unwanted plugin wrappers that jBridger creates after bridging is complete.
    Next, make sure that the following option is unchecked:
    • Create bridging files for 64 bit plugins
    Once you confirm that the correct options are checked, click Create bridging files inside a directory I'll specify.
  4. First, jBridger prompts you to locate the directory containing the 32-bit plugins you want to bridge.
  5. Next, jBridger prompts you to select the directory where you want the 64-bit wrappers to go (again, a subfolder under your main 64-bit VstPlugins directory is ideal).
  6. When jBridger finishes creating wrappers for your plugins, you'll see this message.
  7. Now locate the destination folder that you specified in step 5 and confirm that it only contains wrappers for the 32-bit plugins you wanted to bridge. There should be a TXT file and a DLL file for each plugin.
    Important: Make sure that the files don't have '.32.' or '.64.' in their filenames. In my experience Ableton Live 9 won't display these files in its plugin browser. This is what the 'Don't add .32./.64. in filenames in destination folder' is intended to avoid.
    Also, remember that it's only possible to specify a single VST Plug-in Custom Folder in the File Folder Preferences of Ableton Live, so the directory where your plugin wrappers are stored must be inside that folder.
  8. Now launch Ableton Live. If everything worked, you should now see the bridged versions of your 32-bit plugins inside Live's Plug-ins browser, inside the directory where you saved them.
That's all there is to it! If you don't see any of the plugins that you were expecting to find, make sure to go back through the above steps to make sure you haven't missed anything. If you find yourself having problems with specific plugins, check out the official jBridge troubleshooting page. You'll find lots of answers there.

Vst Plugins 32 Or 64 Bit Iso


Comments are closed.