wetdentist
Synplant, microtonic, IL Sawer & IL Vocodex don't work with bitbridge, barely (and i mean BARELY) work w/ jBridge

microtonic is 64bit now though

I use bitbridge as a default. When it doesn't work, I use j-bridge.
 
Currently j-bridge is essential for 2 plugins that are not in an evolution path:
 
a) Uebershall Liquid series (developed with Melodyne, then dropped by Ueberschall, so not supported nowadays). I used it all the time, the melodyne capability of adapting loops to my melodies is incredible and I started dropping samplers, in particular to reproduce real monophonic instruments (bass, lead guitar). When I switched to 64bit, it didn't work with bit-bridge. 2 years ago I submitted a feature request/bug official mail to cakewalk to have bitbridge work on it, then after months of no reply and successive a, b, c, d version of X1 released with no fix, I resigned to buy jbridge and it worked.
b) the freeware E-MU Proteus VX (again, not developed anymore by EMU), a surprisingly good bread and butter collection of sounds with a '80 feel that I like to keep, along with Dim Pro.

brundlefly
Hey Karl., I was just looking at your old thread about problems with ProChannel and Bitbridge in X1. In connection with resolving that, Noel wrote:
 
"- Go to plugin manager and Take OUT the use jBridge setting at the "folder defaults" level. i,e, you do NOT want to tell the scanner to apply jBridge to every plugin. This is actually a bad idea in general since you are making your system inefficient for plugin processing. "
 
The ProChannel issue was fixed as a bug, but I think he's saying you don't want to do this anyway, because it's going to end up bridging your 64-bit plugins that don't need it.

Glad search is working on this forum because apparently I had set this setting in the past even though I wasn't using the x64 version of Sonar and now with Sonar X3d, jBridge was bridging everything, including vst3's.
I unchecked it, rescanned and now everything is working as intended.
Thanks!