Just moved to 64-bit Sonar X1 Producer Expanded !
 
The ACT and other icons on the top right of the 32-bit plugins are missing as they are under bitbridge. Can they all still work ? Am I missing something ? Is all automation and ACT controls and all that stuff still possible with 32-bit plugins under bitbridge ?
 
Much of the interface at the top of the plugin UI seems different and missing !
 
HELP !

To open the standard VST header for a plug-in running in BitBridge, hold the SHIFT key when opening the plug-in UI. The VST header will be in a separate window and probably open behind the plug-in.

 
Thanks scook. That worked !

I'd be curious your experience with various 32bit plugins. I've been going back and forth with Peter from SonicProjects, trying to determine why OP-X and OP-X II do not save any changes between close/reopens of projects. The other 32bit VSTs (I only have a few I've tried) seem to work ok.  Peter seems to think it has something to do with the way Bitbridge saves the fxb data - it doesn't seem to do it the same way 32bit Sonar does it natively and appears to ignore all program change data. I've reported this to Cakewalk but haven't heard back yet.

Bitbridge is just that, a bridge not only between the 32bit plugin and the 64 bit host host, it's also a bridge between moving from 32 bit 64 bit completely.

I don't think Cakewalk will develop the technology any further as you can easily install both the 32 and 64 bit versions of Sonar concurrently.

Bitbridge is not effective with very plugin. Many of us also use a program called jBridge which costs about $20. If 32 bit plugins are so important to you then perhaps it's worth the price of entry. It has far greater flexibility than Sonar's Bitbridge and can be set as the default bridging software on a per plugin basis from within Sonar.

Very few modern plugins don't have a 64 bit version yet and with the ever expanding formats that developers have to code for I can see a time when some formats will get dropped. Now we have VST 32 and 64 bit for both VST 2.4 and VST3 then there is RTAS for Pro Tools pre PT 11 and AAX 32 and 64 bit for ProTools 11 and onward and that's just for the PC. Add to this the Mac and it's starting to get quite complex.

The best advice is to run 32 bit Sonar for those few older plugins if bridging doesn't work and migrate to full 64 bit. Either that or stay completely 32 bit and deal with any memory restrictions that that implies.

mudgel
Bitbridge is just that, a bridge not only between the 32bit plugin and the 64 bit host host, it's also a bridge between moving from 32 bit 64 bit completely.

I don't think Cakewalk will develop the technology any further as you can easily install both the 32 and 64 bit versions of Sonar concurrently.

I had a different impression based on http://forum.cakewalk.com/FindPost/2892841

scook

mudgel
Bitbridge is just that, a bridge not only between the 32bit plugin and the 64 bit host host, it's also a bridge between moving from 32 bit 64 bit completely.

I don't think Cakewalk will develop the technology any further as you can easily install both the 32 and 64 bit versions of Sonar concurrently.

I had a different impression based on http://forum.cakewalk.com/FindPost/2892841

Seems lately I'm indebted to you keeping me up to date. Another one I missed. That's great news for those clinging to 32 bit plugins that they have issues with. Might look at resurrecting a few myself in the future.

It makes me think about one of Craig's tutorials I was reading earlier today where he mentioned just in passing the reason that the VC-64 hasn't been updated is that the owner of the source code is nowhere to be found. I believe that was Kjaehaus. Again another little bit I didn't know. Thanks again Steve.