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.
This is generally covered at the official How to use jBridge walkthrough, but I've customized these instructions for Live. ONE-TIME SETUP STEPSBefore 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. You will minimize confusion and potential problems by following a similar scheme. Likewise, I have another subfolder where I keep the 64-bit jBridge wrappers for those plugins: I keep all of my VST 2.x plugins in these two directories on my DAW PC:Īnd I created a subfolder where I keep all of the 32-bit plugins that I want to wrap with jBridge:
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.Ĭubase 9 32 Bit Vst Plugins IsoWhat 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. YOU GOTTA KEEP 'EM SEPARATEDMost 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_圆4.dll), that can confuse your DAW and result in unexpected behavior. But before we get started, let's have a quick talk about plugins. These steps should work the same for both version 8 and 9 of Ableton Live Intro, Standard, and Suite.
(There's also a Mac OS bridging solution for 32-bit AU plugins, called 32 Lives.) Please note that while this post is specifically about Windows, there is a Mac OS version of jBridge, called jBridgeM. What follows is what I like to consider the ultimate guide to getting jBridge working with Ableton Live.
I can't get my head around this 'Studio Connections' either.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. Cubase 9 rejects the VST plugins MQ creates, because 32 bit is not supported anymore. I added comments in the video you can't see in the mobile version of youtub.
One final idea might be to use JBridge, that way you can give C5圆4 an 圆4-only folder as well as a JBridge’d folder, and from what I’m hearing that might be a little more stable, depending of course on the plugins, and the 32-bit plugins get to stay where they are you’d JBridge only those that you wanted to use inside C5圆4.Īs to what Cubase does when it finds both a 64-bit and a 32-bit version of the same plugin (e.g.Please don't watch on a mobile device. This is not as easy as it sounds with plugins that have installers, of course, but perhaps you can locate the 32-bit plugins and copy the DLLs?Īnother way might be, assuming that most 32-bit-only plugins will be VST2, you could move some into a subfolder of the main x86 plugin folder (which will change the hierarchy of how they appear in the VST rack as well unfortunately) and then point the 圆4 Cubase only to that subfolder. I would suggest not having any unnecessary 32-bit-only plugins in the 圆4 path, and for those that you really need, make new copies of them in a seperate folder and point C5圆4 at that as well, instead of at the entire x86 folder.
This can be a pain if you have a lot of plugins.