I'm trying to make the transition from 32 bit Platinum to 64 bit. My main stumbling block is all these old Waves plugins. I have tons of CWP files that I created with waves plugins in my templates, and I often have to open old files. It all works fine with 32 bit, all the Waves plugins can be found when I open an old project.
 
Using 64 bit, when I open my template or any old file, it doesn't find the Waves plugins, yet I pointed VST scanner to c:\program files (x86)\cakewalk\vstplugins\ and it has found the Waves plugins and I can manually load  into the FX bin the same missing plugins it can't find. So in other words 64 bit does have access to the Waves and the plugins work fine, but when I load an old project it doesn't find them and I get the Missing Plugins Window coming up.
 
If only I could talk to that window and tell it where the plugins are. Since I can't talk to that window, is there a way to go into the VST scan file and correct the info there and point it to the correct folder where these Waves files are? Even if it's a regedit thing, that's fine with me.
 
My new template doesn't have the Waves plugins, but it'll take many years before I can be in a position to not need to open these old files. I have projects go on for many years.

I think Sonar by default will load a 64-bit version of a plugin that had been initially loaded as a 32-bit one, when both plugin types are in the search paths.  I am not 100 % sure of this, but it is dimly lighting up some synapses in my dusty old brain.
 
There might be a parameter for you to specify the action to take, where you could have it load the 32-bit versions, if desired, but I would think you would want to perhaps accept the missing plugins messages, then swap 64-bit versions for the missing 32-bit ones.
 
Would that work?
 
A long while back, when I moved to a 64-bit Sonar, I did my very best to leave 32-bit projects to continue to open in a 32-bit Sonar (projects with 32-bit plugins loaded), and if I created a 64-bit project, I only loaded 64-bit plugins into it, so I never really had the nightmare of the crashes a lot of folks had early on, and I also made a deliberate decision to use only 64-bit plugins from there on out, other than a small number of 32-bit ones that seemed to work OK in 64-bit Sonar, where there was no 64-bit plugin version available.  Whatever the worth, most of the plugin makers released free updates for purchased plugins to give folks 64-bit versions, and I would suggest you go through that exercise too.
 
Hope some of the above is of use to you - best of luck to you with it all.
 
Bob Bone
 
Bob Bone

robert_e_bone
I think Sonar by default will load a 64-bit version of a plugin that had been initially loaded as a 32-bit one, when both plugin types are in the search paths.  I am not 100 % sure of this, but it is dimly lighting up some synapses in my dusty old brain.
 
There might be a parameter for you to specify the action to take, where you could have it load the 32-bit versions, if desired, but I would think you would want to perhaps accept the missing plugins messages, then swap 64-bit versions for the missing 32-bit ones.
 
Would that work?
 
A long while back, when I moved to a 64-bit Sonar, I did my very best to leave 32-bit projects to continue to open in a 32-bit Sonar (projects with 32-bit plugins loaded), and if I created a 64-bit project, I only loaded 64-bit plugins into it, so I never really had the nightmare of the crashes a lot of folks had early on, and I also made a deliberate decision to use only 64-bit plugins from there on out, other than a small number of 32-bit ones that seemed to work OK in 64-bit Sonar, where there was no 64-bit plugin version available.  Whatever the worth, most of the plugin makers released free updates for purchased plugins to give folks 64-bit versions, and I would suggest you go through that exercise too.
 
Hope some of the above is of use to you - best of luck to you with it all.
 
Bob Bone
 
Bob Bone

The plugins have been converted from DX to VSTs using the Shell to VST program. They're showing up twice in Plugin Manager as VSt.dll and also waveshell.dll. None of this has confused 32 bit Platinum, but it seems to have confused 64 bit Platinum.

Now any of these 32 bit VSTs can be used in 64 bit Platinum if I manually load them into the FX bin, so Bitbridge is working correctly to convert 32 bit plugins to 64 bit. My suspician is it's got something to do with the CLSID file, which is saved deep in the "Users" folder. I have a feeling it's looking for the file from the old project in an old CLSID folder.

This is why I wonder if the solution is more in the registry or some Sonar file. Unless someone seems to have experience with this, I may have to call Tech Support and have them use Teamviewer to figure this one out.


 
Thanks, Bob, nice to see you here,

The fact these are DX2VST wrapped plug-ins is important. Make sure to lead off with this information when talking to tech support. I would be very surprised if 64bit SONAR could ever figure out what is in the legacy files.

If the 32 bit software is loading the 32 bit DX plugin  then wrapping it with the dx2vst will result in the vst plugin being unique to the original and so it will not load.
 
If however you were loading the vst version in 32bit sonar projects it might work.