Do Bitbridge need an re-programming and update, it seems like it to me.

I got this compressor an 32bit, i guess it is based on a 1176 emulation
Audiocation AC1, a nice Compressor Made by : Christian-W. Budde, here's the manual

When you install it as usual in Sonar X3e, it will not show up... ( Bitbridge issue ? )

I got version 1.65 of Jbridge, and tried that to see if i could get the compressor
to work in Sonar X3e, and guess what it works, that makes me happy.

Cakewalk is a Professional company, with "great" developers
so they should be even more capable to get Bitbridge even better.

I don't know the skills about the person(s) who make Jbridge, but he / they
have made a product that seem to work in most cases.

So why is it so hard to get a better functional Bitbride, it is an essential function in Sonar.

I know we are entering the great world of VST3, but still there exists some great
32bit plugins many want to use.

Maybe Cakewalk should hire the guy that made jBridge, or pay him a certain amount to be able to include it as part of Sonar. I have about 5 different VST/VSTi's that would be useless without jBridge.

Leadfoot
Maybe Cakewalk should hire the guy that made jBridge, or pay him a certain amount to be able to include it as part of Sonar. I have about 5 different VST/VSTi's that would be useless without jBridge.

Yes why not ! I think that would be an great idea. Two heads think better than one
and new ideas can be shared for the benefit of better products and new functions and solutions
it will also drop the load of work ea person need to do, at least if they know what they do.

It seems to me , that if you install a 32bit version and a 64bit version of the same plugin
Sonar automatically use the 64 bit plugin and disables ( excludes ) the 32 bit version, as i understand it !
Correct me if i am wrong !

Think if this : If we could have Jbridge implemented and you just install the old 32 bit plugin as usual
and Jbridge do the rest and automatically, create a working "64bit plug" and disables / excludes the
orginal 32bit plugin.

Now that would be nice, but then again isn't Bitbridge already doing that, atleast try to 

The best practice is not to have the 32bit versions of plug-ins in a location where the 64bit VST scanner can find them, if there is a 64bit version available.
 
Through X3, BitBridge was a third party product. Cakewalk now owns the source code. No bridge technology is perfect and is primarily intended as a temporary solution while transitioning to a 64bit environment. Most software that is exclusively 32bit is not being maintained at all. Reliance on old, unsupported third party software is not a good idea.

scook
Most software that is exclusively 32bit is not being maintained at all. Reliance on old, unsupported third party software is not a good idea.

That may be so, but the thing is, I paid $800 for Focusrite Liquid Mix when it first came out, and I still love the sound of it. So I want to use it for as long as I am able. JBridge makes that possible.

To which I would add the #1 source of tech support headaches at Cakewalk is third party plug-ins...another reason why Sonar includes so many plugs. That way you don't have to deal with plug-ins that may or may not have been tested with Sonar. 
 
Bridging will always be a "kluge" technology. At a PreSonus user conference, someone asked Studio One's developer what the solution was for using 32-bit plug-ins with the 64-bit version of SOP. His answer was "tell the manufacturer to develop a 64-bit version." I think one reason why new users find Sonar X3 so stable is because they're not using a lot of legacy plug-ins.

There are a handful of abandoned x86 VST2 plugins that I really like - the entire Kjaerhus collection comes immediately to mind. And in fact I think that may be the last of them. And I am pretty sure they will never be updated, so I continue to look for alternatives.
 
In the meantime, if a developer is still actively developing then I expect them to come up with an x64 version of their plug-ins... heck, I kind of expect them to come up with a VST3 version<G>!
 
It takes time, I understand that, I spent way too much time developing commercial software!
 
And it is not something that can be easily scheduled. You might think you'll have it done by a certain date, but until it is done you never really know. I understand that too.
 
But I also understand that ANY bridging trick is just that, a trick. And it should be used carefully, and cautiously, and sparingly. Some here probably remember the VST to DirectX bridges, one of which Cakewalk did buy. They had their problems too. And eventually most of us abandoned any plug-in that did not come in a VST format.
 
Frankly, if I paid any amount for a plugin I'd be asking the plugin developer to fix the problem, I would not be depending on a trick to get me by. Focusrite is a pretty upstanding company - I'm pretty surprised they have not updated it. But if they haven't, and if they have no plans to do so then you do have a big problem.
 
And I do sympathize!!! There is NOTHING more frustrating than losing the use of a software tool for which you paid good money, in good faith. Sadly, there are quite a few software developers that do not think they have any responsibility to their customers. The equivalent of the age old "trunk slammer". And most of us will get burned by one of these clowns at least once.
 
Anyway, if you are using this as a hobbyist then you are probably stuck. If you are using this professionally then I'd take a look at what income you have earned as a result of owning LiquidMix, and writing it off as a lost cause if possible. Not fun, pretty distasteful in fact, but probably necessary. Sorry!

wst3
There are a handful of abandoned x86 VST2 plugins that I really like - the entire Kjaerhus collection comes immediately to mind. And in fact I think that may be the last of them. And I am pretty sure they will never be updated, so I continue to look for alternatives.
 

FYI - I love the VC-64, which was done by Kjaerhus, and asked why Cakewalk can't update it. They have tried everything to locate the original developer, but as far as they can tell, he has disappeared off the face of the earth. They can't secure the rights to the code or an updare from the developer because they can't find the developer. It's too bad, really. I have a bunch of FX chains that use the VC-64 and at some point, they will become unusable. i can replace some of the presets, but not those which took advantage of the VC-64's parallel processing.

I am right there with you Craig, VC-64 is awesome, as are the old Golden Series processors, heck, even his freebies collection had some real gems. And while I'm not sure what the thought process was, I ended up skipping the "Golden Channel" because I liked VC-64, and didn't see much of a difference between them.

I know the original developer gave up developing, did not know that he disappeared.

It's bizarre that nobody has a clue whatv happened to him. I love vc64