in Ableton this is no problem. bridged and “original” are treated the same.
In Cubase a bridged plugin is still considered a “different” plugin and therefore it’s settings in a project that was created containing the unbridged plugin will not be loaded. Still the same in C7.
What do you mean by “different”? You don’t want Cubase to see the original plugins, because that could create conflicts between jBridge and VSTbridge (Cubase’s own bridger), which would likely result in a Cubase crashing on start. So, keep them in a folder that Cubase won’t scan (they still need to be in the Program Files (x86) folder though.)
Start jBridger and click on “I’ll be using a x64 host.” Then you get to another dialog box where you can choose additional options. Click on “create bridging files inside a directory I’ll specify.” Underneath that button there’s an option ("don’t add .32/.64 in file names in destination folder.) Keep that one unchecked and all your bridged files will end up with x64.
I’m assuming the OSX jBridge is identical to its windows counterpart, but it’s possible that a few things might be different, or just placed differently.
Both OSX and Windows see the bridged VST as separate from its x86 originator. Like I said, you should keep the original x86 VST’s in a folder that Cubase does not access.