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. 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. 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_圆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.