Since I still have and use quite a few vst and vsti's that are only 32 bit, not 64 bit, I have them all set to use jBridge instead of bitbridge for bridging purposes.
To do this, each and every 32 bit plug needs to have it's properties dialog box opened within plug-in manager and set to use jBridge. This is very time consuming.
Doing a reset will remove that preference and set it back to using bitbridge.
To use jBridge on all the 32 bit vst and vsti's, they all have to be set individually, again.

Why do I prefer to use jBridge over bitbridge?
I've got 100% stability using jBridged whereas I have a few plugs that will crash Sonar bitbridge/teleport server error if using bitbridge and with jBridge, the plugin isn't always on top and the additional preset management.

Just an FYI.

Unless I'm misunderstanding you here, sounds like you are over complicating matters a bit to me. I certainly didn't have to do any of that to use Jbridge. I keep all my jbridge wrapped plugs in my C:/program files/cakewalk/vstplugs/wrapped plugs. I launch the jbridge exe " jbridger" select the x86 folder that contains the plugs to be wrapped and choose the CW vst folder as destination. Rescan and it all works.
 
Edit: Forgot to add, ensure that the x86 vst path of the plugs you have wrapped, is not present in your vst scan

After installation of X3D patch a reset is generally a good idea, but don't take it from me, full info here:
http://www.cakewalk.com/Support/kb/reader.aspx/2007013315
 
..should you choose not to take this advice, well that's up to you... But if there's something wrong with your plugins and you didn't do this, that's generally the next thing to try.
 
I'm not sure what else to suggest.
 
Cheers...

ohgrant
Unless I'm misunderstanding you here, sounds like you are over complicating matters a bit to me. I certainly didn't have to do any of that to use Jbridge. I keep all my jbridge wrapped plugs in my C:/program files/cakewalk/vstplugs/wrapped plugs. I launch the jbridge exe " jbridger" select the x86 folder that contains the plugs to be wrapped and choose the CW vst folder as destination. Rescan and it all works.

If I ever have to reset and rescan again, I'll try what you did.

IIRC the folder defaults button in plugin manager allows you to apply the JBridge flag to ALL plugins in the scan path. The next reset and scan will pick up the Jbridge default.

Noel Borthwick [Cakewalk]
IIRC the folder defaults button in plugin manager allows you to apply the JBridge flag to ALL plugins in the scan path. The next reset and scan will pick up the Jbridge default.

Yes it will Noel but it will also apply jBridge to all 64 bit vst2 and vst3 plugins too.
If it could be done to each path separately instead of all scan paths inclusively, that would be greatly helpful.
I put that in as a feature request.

The main reason why bitbridge sucks is that it makes presets unusable for a lot of plugins. There is nothing wrong with loading jbridge on all 32 bit plugins - it's a good idea. And yes it's a PIA to have to go back and tick all the boxes for each plugin after a reset.

Noel - I wish you guys would tell us what you have changed regarding plugin handling. Something has definitely changed since X2, and it's still changing in the X3 patches - why else would we have to reset and rescan all our plugins?

I can tell you for sure that it has broken my DMGAudio plugins. At least if we knew what's been changed - we could tell the developers, so they could fix their plugins. My 2 favorite plugins (Equilibrium and Compassion) are unusable for me right now.