32 bit plugs in X1 and X2 64 bit

It is BitBridge in Sonar - I think there is a JBridge out there that may do it better - others can advise on this.
 
I made the choice to limit myself to 64-bit Sonar and 64-bit plugins some time ago, except where absolutely required, and for those situations I use 32-bit Sonar with 32-bit plugins.
 
While a great many folks ARE using some number of 32-bit plugins in 64-bit Sonar, I just don't bother with it at this point, and I have a nicely stable and powerful system that never crashes.
 
Bob Bone

Donny, I'd have to agree with Bob. If you like 32 bit plugs, use Sonar 32. I use 32 religiously on this end because I've had a bit too many problems with bit bridge and my 32 bit plugs. I do not think it is the fault of Sonar....as I have had a few issues with others I use. But whenever Sonar 64 crashes, that teleport server thing is up in task manager. Also, bit bridge doesn't have my presets in the menu window all the time. Some plugs have them, others do not. Using J-Bridge, you get your plug presets all the time...so that's a plus.
 
At the end of the day, I don't use loads of synths to need 64 bit power. I have powerful enough pc's that can run 32 bit without drop-outs, clicks, pops or other performance issues. I don't even need to freeze tracks and honest, I run huge projects over here. But most are audio without large sampling libraries. So if you're like me and have a good pc with a strong processor, Sonar 32 should be fine. If you need the extra power and must use 64, try J-Bridge for your 32 bit plugs. Just beware you *might* see some anomalies from time to time. When I use Sonar 64 with nothing but 64 plugs, it doesn't give me an ounce of trouble. Sometimes 3rd party plugs may mess with me that are 64 bit, but for the most part...Sonar 64 only drives me nuts when using 32 bit plugs...so I just stay away from it. It doesn't always mess with me, but when it does, the first thing that comes to my mind is "why did I use 64?"
 
Another reason I don't use 64 is I have a few old DX plugs that I can't do without which of course would need to be wrapped if I tried to use them in Sonar 64. I definitely don't want to do that...so in 32 I stay for now. I do use 64 from time to time when I need the big sampling libraries at once though. I just stay away from 32 bit plugs...which I've just about updated all of them. You mention waves...they have 64's now so see if you can update. I have about 8-10 plugs that are still 32 that I rely on. I can do without them in some situations...but not in others. Good luck with everything.
 
-Danny

BitBridge works just fine with many 32b plugins in Sonar x64. 
Before buying J-Bridge why not start by trying a few 32b plugins in your in x64 projects & see how well they work? 

Quite correct on the memory access, and also a good point on trying things out with BitBridge prior to laying out cash for JBridge.
 
IF you experience issues with 32-bit plugins using BitBridge in 64-bit Sonar, then you can either:
 
1. Use a 32-bit Sonar install to deal with 32-bit plugins for the project at hand or for all projects
2. Try out JBridge for the project at hand or for all projects that use 32-bit plugins in 64-bit Sonar
3. Make a choice to rely on 64-bit plugins only for the project at hand or for all projects.
 
My vote is still for opting for using a 32-bit Sonar install when working with 32-bit plugins.  Such an arrangement has been rock solid for me, and I believe for Danny as well, but there is nothing at all wrong with using a bridging program to continue to use 32-bit plugins with a 64-bit Sonar installation.  Lots of folks do any one, two, or even all three of the above, as well as the set of folks for which BitBridge works too.
 
The only wrong choice I can see is attempting to repeatedly have crashes occur that are caused by some sort of issue using a 32-bit plugin in a 64-bit Sonar install.  That's just beating your head for no productive reason, and yet there have been all kinds of threads from folks who for whatever reason keep crashing and building frustration levels, when there are alternatives that work with far more stability.
 
Hope that helps, 
 
Bob Bone
 
 

dupe....

Personally, the bridging part of the 32-bit from 64-bit is that on my machine, I lose some CPU resources for the actual bridging, and this is a 4/8 Core/Thread iCore7 CPU. Normally, in 32-Bit Sonar, I can mix 40-50 tracks, each with up to 3-4 plug-ins (if necessary, including Console emulation) and not flinch. Using 64-Bit Sonar with bit-bridging I can only mix about 20 tracks before drop-outs become a serious issue. That's something I have found that made me keep 32-Bit Sonar installed. 

jBridge can also be used to run 64-bit plug-ins in 32-bit Sonar, besides running 32-bit plug-ins in 64-bit Sonar like Bitbridge (and can also bridge between 32-bit plug-ins and 32-bit Sonar.)
 
Vienna Enemble Pro also offers such functionality, both on the same system or on a remote system, albeit at substantially higher cost (but with substantially more features) than jBridge.
 
That said, there are plenty of buggy plug-ins out there (both 32-bit and 64-bit) so... ymmv