Great that you got this solved! And good that you shared your insights about 32 bit vs 64 bit from the look at the Cantabile log - giving as much context as possible is essential for other forum members to be able to help you. Too often, we have posts like “I DON’T GET ANY SOUND - CAN YOU HELP”…
BTW: the “typical” place for VST2 plugins is C:\Program Files\VstPlugins (or C:\Program Files\Steinberg\VstPlugins if you are a Cubase user) for the 64 bit versions, and C:\Program Files (x86)\VstPlugins for the 32 bit versions. Helps to not confuse them.
But of course it is perfectly OK to have one overall VST folder for all plugins, with sub-folders for 32 and 64 bit versions, as long as you keep your plugin path settings clean within your audio software.
Unfortunately, some VST2 plugin vendors are not as flexible, and they force a certain plugin path - Roland being an example, whose installation manager refuses to cooperate, unless the plugins sit in C:\Program Files\VstPlugins. But that’s another story…
A word on jBridge: when you use jBridge, you usually need to create explicit “bridging” wrapper plugs in the 64 bit folder that point to the corresponding 32 bit dll in the 32 bit folder. This process of creating these wrappers is called “jBridging”. But note: Cantabile doesn’t need you to jBridge your plugins, because jBridge support is built into Cantabile - once jBridge is installed, Cantabile 64 bit can directly scan and recognize your 32 bit plugins without the need to create the 64 bit wrappers.
But to use them in other DAWs, you might need bridging - see @Derek’s post: 32-Bit VSTs in 64-Bit Cantabile - #3 by Derek . So your VST folder might need three subfolders: “64 bit”, “32 bit”, “32 bridged”.
In any case: when you’re using jBridge, be absolutely sure that you don’t have the same plugin in 32 and 64 bit version in your plugin scan path - this is a potential source of issues, so steer clear…
Cheers,
Torsten