32-bit plug-ins on 64-bit system?

They don't dock because they are loaded through Bitbridge which always sits on top. As for Isotope Vinyl, is it a DX plug-in only? If so it won't show up in 64 bit SONAR (no 32 bit DX stuff will), try to see if there's a vst version available.

Bump.

I'm also seeing that when I use Battery 2 (which is 32-bit), and load up a project from before, the synth is not found, and there's no way to find out which kit I used, so I have to re-load Battery and start all over with any settings I had before.   Annoying, given that I have many projects that use Battery.  Do I have to install the 32-bit version of Sonar X1 as well to use old projects?  Seems rather silly that projects made in 32-bit don't open properly in 64-bit.  

Is anyone else finding this when they go 32 to 64?

If you run the Vinyl installer again it should give you a 64 bit version to install. Doesn't help your issue but a native 64 bit plugin is always desirable over one that has to be bridged.

Thanks for the replies guys.  I installed X1 32-bit last night and could load my existing projects ok.  For the most part, I don't have a problem re-developing things for the new version, but if I put in some work earlier, I don't like losing that either.  I also tend to use mostly the stuff that came with Sonar, and those plug-ins adapted ok to 64-bit.  So, I think moving forward, I'll finish existing projects in 32-bit, and start new ones in 64.

I also downloaded and installed jBridge, which at first, totally crashed Battery 2, but after the Windows 7 security fix, it works well.  On a related note, I might just upgrade to Battery 3 anyway - does anyone know if it's 64-bit?  Also, Battery 3 is already a few years old - should I just wait a while for Battery 4?

Thanks guys!

You can rename plugins, but it won't help you because the name you're allowed to alter is just a display name and does not change the identity of the plugin. 

That's because plugins are identified internally by a CLSID (Class ID), a 36-character string of gobbledygook stored in the CWP file that correlates to an entry in the registry. That registry entry is created when the plugin is installed, and it's how the DLL is identified internally regardless of what you name it.

The vendor creates the CLSID and is responsible for making sure it's unique in the world. If there are two versions of a plugin, each must have its own CLSID so that DAW projects can differentiate between the two.

Here's where problems sneak in: whenever the vendor releases a new version of the plugin, he has to decide whether or not the new version will inherit the same CLSID from the previous version. Often, it's perfectly OK to keep the same CLSID. That way, you simply drop in the new DLL and just like that the plugin is updated. SONAR sees it as being the same plugin because it has the same CLSID and is not concerned that it's actually a different file. Minor fix releases typically work this way.

But if the new version adds significant new features, then it must be given a new CLSID (and usually, a new file name as well). When you add a plugin to a project, it informs SONAR about its capabilities, such as which parameters can be stored and automated. This information has to be associated with a specific CLSID. For example, if you have both Ozone 3 and Ozone 4, you'll see in the registry that each has its own CLSID, and they are separate DLLs. This allows you to have both present in the same project, because SONAR treats them as two separate entities.

I'm guessing that what happened is you installed an updated version of the plugin because the old version was not 64-bit. In the process you actually installed two brand-new plugins, each with its own CLSID, both different from the previously-installed version. Neither is a direct replacement for the old 32-bit version, which was never installed on the new system. If that's what happened, you should be able to re-install the original version all would be well with your old 32-bit projects again. 

So what is the best installation approach to take if starting from a new system build in order to get 32-bit plugins running on a 64-bit version of Sonar?