Hi all,i use the great Jbridge couse save my life with Liquid Mix.It's awesome!!! check my thread...http://forum.cakewalk.com...347848&mpage=1#2348240 best Roby

I found I needed Jbridge for BFD Eco - It worked with bitbridge but crasehed with teleport server errors occasionally, with Jbridge is still has a couple of minor issues but nothiong that stops me from using it. Kitcore is the other application I find need Jbridge.

I didn't know about the "presets" thing. Hmmmm.

That's the main reason I use jbridge - for preset management.
 
Bitbridge is useless for this...

I have strange issue with jBridge - it loads 64bit plugins like Kontakt and GR5 automatically, even without chacking it in Plugin Manager.

And GR likes to crash. Moreover, even If I'll uncheck "load using jBridge" - it still loads using jBridge!!!!

****in miracle... :-/

Bub

I've never had a problem with B or J bridge.

That's probably because I don't bridge any of my x86 plug-in's and I don't own J bridge.

Honestly, the best solution would be to fire up X1 x86 and save yourself all the aggravation that goes along with bridging. It's one of those unnecessary evils that people put themselves through IMO.

If you want to work in a 64 bit environment, then freeze that track in X1 x86 and fire the project up in X1 x64.

HTH

To each their own, I guess.

For many of us, with jBridge and/or Bitbridge, the 32 bit plugs are there and working in 64 bit.  Once the plug-in is set up, it just works seamlessly.

How in the world is that an "unnecessary evil" compared to having two versions of Sonar installed, and being forced to go back and forth between them?  Your method seems like a PITA last resort option -- certainly not one that's preferred, or even more convenient. 

IMO, of course.


 

JonD:

I see you've met Bub. LOL

Yor Ol Pal:

I use jBridge over BitBridge because I like the ability to have the Give all keystrokes to plug in button, stepsequencer button, Read-automation button, write-automation button, and solo button easily accessible on the GUI of my bridged plug ins.

You have to open the plug in GUI while holding down Shift, to have these buttons accessible using BitBridge, and even then it's two windows open, which is not attractive to me.

With jBridge it's one GUI window, which looks nice. :)

Also jBridge retains significant features of my 32bit plug ins. For instance, I still use the DR-008 drum sampler. When I use BitBridge, and save a project with a kit loaded into the DR-008, upon re-opening that project, the kit is not automatically loaded as it is when I'm using the 32bit version of SONAR and the DR-008. And I have to go through the red tape of browsing to load the kit back into the DR-008, everytime!
However, if I use jBridge, the kit I saved is automatically loaded when I re-open a project I saved with a kit loaded. That's a somewhat little thing, but it matters to me. :)

With jbridge, I can be focused on the plugin and when I press the space bar, the track still plays.
 
With bitbridge I gotta click out of the plugin, onto sonar to playback - this is definitely annoying.
 
Lance

I wish there was a way to switch bitbridge off and use only jbridge insread of having to do it on plugin by plugin basis.

mudgel
I wish there was a way to switch bitbridge off and use only jbridge insread of having to do it on plugin by plugin basis.

While AFAIK it's not possible to switch bitbridge off, it is possible to set jbridge as default on a plugin "category" basis. **
 

• Open the plugin manager click on the Category type in the left hand list.
• Click on options in the "VST configuration" section
• Click folder defaults in the dialogue that opens
• Check "Load using jbridge wrapper" and okay your way out.

 
HTH
 
 
** See brundlefly's post below this one though.

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.