• SONAR
  • Why do use JBridge over BitBridge?? (p.4)
2013/10/13 04:36:03
Loptec
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
2013/10/13 04:55:37
FastBikerBoy
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.




Thanks Dave. Now you come to mention it I do remember that thread. Seems like I'm dishing out bad advice.
 
I think I've made the same mistake here of assuming that nothing would be bridged (by either bitbridge or jbridge) unless needed. That would seem to be the logical behaviour to me. Guess I shouldn't go assuming anything. 
2013/10/13 07:02:36
fcarosone
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.
2013/10/13 07:10:15
Glyn Barnes
emwhy
Some of my vsts just would not work correctly under Bit Bridge, Drumagog, the Korg Legacy Suite. These are go-to plug-ins for me especially Drumagog.


The Korg Legacy Suit is now available in 64 bit.
2013/12/30 08:55:50
gustabo
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!



2013/12/30 10:46:22
lawp
Loptec
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


as is IL Sawer (and I also have x64 native versions of Harmless & Drumaxe :))
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account