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

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.

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

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.

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 


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 

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

 

JBraine is correct-there is no copy, makes no sense. Highlight the VSt in CW plug manger-click properties and check Jbridge, That's it.
Simple-Copies just makes no sense at all-sorry.
Doesn't matter how many plugs you have . Once ticked the vst will always use Jbridge.
To undo that just un tick the box

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.