I have an approach that has been working well for me now, and gets around the bridging mess that can occur if you have a DAW on the same system as Cantabile.
I make 6 VST plugin folders, not counting VST3.
VST Plugins 32 Bit
Hidden VST Plugins 32 Bit
jBridged plugins 32 bit
VST Plugins 64 Bit
Hidden VST Plugins 64 Bit
jBridged plugins 64 bit
The 32 and 64 bit folders host plugins directly, with a view to having them directly available in a host that understands them, without bridging.
The ‘Hidden’ folder is home to plugins which need to be bridged, and avoids double bridging when used with hosts like Cantabile which have integrated jBridge into the app.
The ‘jbridged’ folders host the bridged files that apps with no built in bridging require, and allows jbridge to to create those files using its recommended file structure (i.e AWAY from the original files)
A 64 bit Cubase will NOT be pointed to the Hidden files. It will look only at the 64 bit jbridged files and the regular 64 bit unbridged files.
A 32 bit Cubase will NOT be pointed to the Hidden files. It will look only at the 32 bit jbridged files and the regular 32 bit unbridged files.
A 64 bit Cantabile WILL be pointed to the Hidden files because Cantabile makes its own jbridge files. It will also be pointed to the regular 64 bit files.
A 32 bit Cantabile WILL be pointed to the Hidden files because Cantabile makes its own jbridge files. It will also be pointed to the regular 32 bit files.
It’s a lot easier to maintain this structure than try and work out a mish mash of plugins afterwards,