I've got like 6-7 locations for 32bit plugins, how do I install and configure J-Bridge to see them all? 

I tried installing J-Bridge once already and it more/less disabled all of my 32bit plugins. 

MOST of my plugins are STILL 32bit, so this is an issue I'd hope to resolve. 

Also - of those of you using J-Bridge, did you really notice better performance on 32bit plug ins?  

HALP! 

Thank you kindly... 

-G&G

I don't think you can make jbridge the default bridge.(I hope I'm wrong but this is what I did) go to the plugin manager screen where you manage the plugin list. and click the vst section, then click on a 32 bit plugin to highlight it, then click on the plugin properties button at bottom of the dialog and finally check the box that says "load using j-bridge wrapper". It's one by one as far as i know.

thanks - 

can someone detail the process in steps... I'm still confused, sorry. 

Hello there.
For me Bit Bridge works for all of my 32 bit plugins.
How does BB not working for you?
Can you detail it, and maybe we can help.

dan le

gear

Sorry to hear your having issues....jbridge is a bit confusing.....however it is simple once you figure out how to get  it to work for you......but like you I struggled a bit.....

Now this is just what works for me.......

I have a 64 bit machine but I still have a few 32 bit plugs that I still love and am unwilling to get rid of......the answer starts (at least for me) with "where" you put your plugs (dll files).............

Here is what I do......

In my Programs file (in the c drive) I have placed one folder labeled "All VSTs"
I then sub folder it:
64 bit VST's
32 Bit VST's
Cakewalk Vst's
jbridge VST's

From this point you can subfolder inside of each of these further if you wish....(I do because it keeps it simple to find stuff at least for me..)

Now when you install a program point the vst to the correct folder.....
64 bit VST's go into the 64 Bit folder
32 Bit VST's go into the 32 Bit folder
etc.......
But you do "not" place anything into the jbridge folder.....as this is the destination folder that jbridge will place your jbridge scanned dll files into.........so in essence all jbridge scanned dll's will land there! Understand?.....so your going to scan your 32 bit folder and when jbridge askes where to find the 32 bit dll and then it is going to place it's copy of that dll into the jbridge folder...........in essence a jbridged plug will then be established.....

Once you establish this folder system you will need to go thru all of your programs and move all your dll files into the appropriate folders.....a bit of work up front ...yes .....but cleaner and a lot more organized..... if something does not work then you know exactly where to go find it!!!!!!!  see?

Once you get jbridge installed then the rest is easy......
"You just need to keep in mind that jbridge needs to know where your original 32 bit vst is (your 32 bit folder) and where to place the jbridged 32 bit vst......(the jbridge folder.....)

so in other words......have jbridge look in the 32 bit folder for your unscanned jbridge dll file and then it will place the jbridge scanned dll into the jbridge folder for you.......

Now when in sonar and you need to have your plug in manager scan your vst's..... well all you need to do is point it at your "All VST's" folder and it should pick up everything!
 
one slick folder to scan and bam.....onward........also the scan will go faster cause it does not have to "search" all over for things..........and if you defrag on a regular basis it will keep things nice and tidy......... 

When you go to insert a plug in a project be it track or buss then your drop down box will list your four folders;
64 bit vsts
32 bit VST
Cakewalk Vst
jbridge Vst
and if you have each of the above folders subfoldered further (ie....ik multimedia, PSP, Softube, fabfilter etc..) these will then show under that folder so you will be able to find your desired plug a LOT faster!
no more searching around, or trying to remember where everything is etc......... and if it is a jbridged plug you will know wherre to find it and you will know that when inserted it will be a jbridged (and not a bitbridged) version of the plug.........so in essence you have a choice of how that plug will work......see?


Just my two cents.............
I hope it helps
Clifford

Thanks - I'm gonna try it. 

I get a little spooked manually putting plugins into different folders/directories... but I'll give this a shot. 

At this point, are all Cakewalk Native Plugins 64Bit? 

Was Pantheon 64bit or 32 Bit? 

Trucker,
 
It's not that complicated. jbridge works with SONAR - it doesn't copy plugin files or make "jbridge versions" - that is for apps that don't directly support jbridge (like SONAR does.)
 
All you do is:
1) install the jbridge programs (I can't remember if you have to tell it where your plugins are or not)
2) if you want to use jbridge for a plugin just do like frankjcc says - find the plugin in plugin manager and edit properties and tick the jbridge does. This *does* create a text file in the same place as your plugin (with the jbridge settings) - but it doesn't create another copy of the plugin. That is for *non SONAR* applications.
 
It is simple. ;-)
 
gearandguitars - jbridge doesn't make your plugin "perform" better - but it makes some plugins "work" that don't work with bitbridge. Also - I fine that bitbridge is lousy for saving presets, or even loading presets that you already have - where jbridge works with presets like "normal". I use jbridge for all my 32 bit plugins.
 

jbraner


Trucker,
 
It's not that complicated. jbridge works with SONAR - it doesn't copy plugin files or make "jbridge versions" - that is for apps that don't directly support jbridge (like SONAR does.)
 
 
*Well when I want a plug in to use jbridge for a specific plug in I open the jbridge program tell it where to find the plug (my 32 bit folder) and then where to place it (the jbridge folder) and then a new jbridge dll shows up in the jbridge folder......so in my view point it does create a jbridge version of the dll......
 
*and yes jbridge was a bit to figure out the first time I used it..........
 
 
All you do is:
1) install the jbridge programs (I can't remember if you have to tell it where your plugins are or not)
 
 
***Yes you do have to tell jbridge where your plugs are located and if they are in different locations the searching for them and chance of error and missing some is highly likely...
 
2) if you want to use jbridge for a plugin just do like frankjcc says - find the plugin in plugin manager and edit properties and tick the jbridge does. This *does* create a text file in the same place as your plugin (with the jbridge settings) - but it doesn't create another copy of the plugin. That is for *non SONAR* applications.
 
It is simple. ;-) 
 
  
****All I'm saying is that when I go to install any plug in I place it in the correct folder I have laid out for my self......this way ALL my plugs are in ONE location. they are seperated out by my four folders.....When I go into my plug in manager I have only one line of text for it to scan......it cannot get any easier....
 
I used to let the plugs install where they wanted to (which is what I believe that you are suggesting ) but I ended up with my plug in manager being very messy because it had so many places it had to scan for plugs and if I had an issue I spent hours trying to straighten it out because I had to keep looking for the plugs location etc............one total mess....
 
Now that I put everything in one place my plug in manager has only one line to scan!!! and that would be my "All VST" folder on my C Drive...........how can it get any eaiser???????  
 
 my question to you is why in the world would I want to have to go into the plug in manager, edit text, tick check boxes etc....when all I need to do is open jbridge point it to where the plug is and where to put it?
 
To me that is so much easier...........
 
Just saying!
Clifford

Something is being missed by one of us ;-)

Of course it makes sense to put all your plugins in one place - that's the sensible way to do it ;-)

I'm not sure what you're talking about re: enabling a plugin for jbridge though. Ticking the box is the only way you do it in SONAR. Anything involving 'running' jbridge and making a copy of the plugin dll is not the way you do it in SONAR and is definitely over complicating things. I'm not really sure what's complicated about ticking a box once to enable jbridge for a 32 bit plugin - but that is how you do it.

I'm pretty sure that somehow we're talking about two different things here...

I think it depends on how many plugins you have as to which one makes sense. if you only have a few 32 bit that you couldn't do without then ticking the box makes sense. If you have hundreds that you just want to have Justin Case then you might want to kind of automate things. What I really dont get thought is If I have all of my 32 bit plugs using J-bridge, why do I still get bit bridge hanging on close in some projects.