OK, Like I'm a 2yr Old... How to Install J-Bridge on X1?

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

thanks - 

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

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

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.
 

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...

jbraner


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...

 
 
 
Well I do not think I spoke of "enabling a plug for jbridge"...??????......I don't think I would even know how to do that......
 
I do think I know where we are not connecting........
If I understand you correctly
You open your plug in manager
highlight a plug you want to use as a jbridged plug and then
edit some text
check a box
and then ???
where does jbridge put this plug??? if you have an issue with it could you find it to fix it ? or would you have to search for it???   What if one of your plugs can use bit bridge or jbridge do you get a choice??? 
 
See to me I do....I know which plug I am going to use and what bridging program I will be using it with.......the way you have it explained I do not have that same feeling or understanding.......
 
What I am saying is
go to the start menu
open the jbridge program
when it ask's what plug in I want to use jbridge on I browse to my 32 bit sub folder and highlight the plug in
then the jbridge will ask where do I want to place it so I choose my "jbridge sub-folder"
click
Done
 
we have two differnt ways of doing the same thing........only for me it makes a lot more sense because ALL the plugs that I use jbridge for are in One sub folder (of my master VST folder)....
 
In other words this gives me the ability to say jbridge take this 32 bit program and do your thing and place your results in your own folder......now anytime I want to use that program jbridge will go to the jbridge sub folder and open that plug in from there
 
that's all I'm saying
Clifford

jbraner


Clifford,

OK I'm understanding what you're saying now - but whether you know it or not, you *are* indeed telling jbridge to make a copy of the dll to its own 'jbridged' plugins folder.
*****This is exactly what I've been saying all along.**********
The way I'm saying to do it - leaves the dll exactly where it has always been, and just happens to create a text file next to it (which you will never use because you make your jbridge settings in the plugin screen and jbridge uses the text file to store those settings.)
 
****and this is exaclty what I do not want to do......leave it there......I want it in it's own file plain and simple....easier to find and work with for me********

If you enable a plugin for jbridge then it doesn't use bitbridge, and vice versa, if you don't enable a plugin for jbridge it uses bitbridge by default.
****** I ask jbridge to enable my 32 bit plugs unless that plug does not like jbridge ....then I leave it alone and let it use bitbridge.......I would say that larger bulk of my 32 bit plugs are happy with jbridge......it is only a few that do not......so I leave them alone......and yes I have 32 bit cake plugs that are perfecltly happy to be used by jbridge so I do so....
 
It is very simple.
You shouldn't ever have to 'run' jbridge - you just install it once and forget about it. Trust me - its in the manual 
 
 
****ok.......but I LIKE they way I have it work now and am not willing to change.........it works for ME******


Yes - install all your plugins to one place (in their own sub folders) - but don't use jbridge to make another copy of them somewhere else (all in one other place). That doesn't make sense. That is what you do when your sequencer doesn't directly support jbridge - but SONAR does directly support jbridge 

****You know I hate to say this but it makes perfect sense to me ...in fact once jbridge makes it's copy I will actually go into the 32 bit folder and delet the original dll file and jbridge file and jbridge text file etc.....it just makes it so simple and clean for me........ I do not see the advantage of doing it your way....that does not make sense to me.......that is just my way of working and I am happy with it so I see no reason to change........it's just simple :-)
 
Have a great week end

 

I will actually go into the 32 bit folder and delet the original dll file and jbridge file and jbridge text file etc.....it just makes it so simple and clean for me........

I'm not sure how that is simpler than doing nothing - except ticking a box
The vst files should all be organised and "clean" in the first place.
 
 

I do not see the advantage of doing it your way

The advantage is that:
1 - this way is easy
2 - you can go back and forth between jbridge and bitbridge (to see which works better for your particular plugin) by simply ticking or unticking the box.
 
Trucker - you have a great weekend too (it's Saturday here, so mine is already started). No one is going to convince you that your way is not the best - so carry on, and enjoy! ;-)
 
Everyone else  (including gearandguitars who started this thread) - judge for yourself, but in any case jbridge is not difficult to set up or use.