Converted to 64 bit, now plugins not found

Guys,

I went from 32 to 64 bit when moving to X1 (including a new machine with Win7).  I have a lot of projects now that have missing plugins because of this.

Is there an easy way to point to the 64bit plugin, so I don't loose my settings on the plugins?  Or am I looking at mixing all tracks again on old projects?

Thanks!
Aldwyn

I did not install the 32bit plugins...  so the path is gone.  I was hoping I could point the projects to the 64bit plugins which are there, and not loose my plugin settings.

Thanks!  I wonder if I make a link from there to the 64 bit plugin dir if it will work... experiment time.  :)

Hey Aldwyn,

When I moved to 64 bit I still installed my 32bit plugins. Sonar brings up a "Locate VST Plug-in" window and there I can choose the 64 bit even though I made the project with the 32bit version. The only reason I can tell the difference between the two is where they are located. The 32bit ones are in the (x86) folder and the 64 bit ones are in their own location.

Yours are obviously coming up as missing and you have no option to choose a replacement or you wouldn't be here. The only thing I can mention is to be sure all of your VST plug-ins file locations are selected in the "manager tool" and you have scanned them. If this doesn't work you might have to install your 32 bit versions just so it points to them so you can choose the 64 bit version.... IF that works.

Sonar should be seeing them so long as they have been scanned,

Rob

Aldwyn


Guys,

I went from 32 to 64 bit when moving to X1 (including a new machine with Win7).  I have a lot of projects now that have missing plugins because of this.

Is there an easy way to point to the 64bit plugin, so I don't loose my settings on the plugins?  Or am I looking at mixing all tracks again on old projects?

Thanks!
Aldwyn

Dear Aldwyn
 
Did you clean sweep installed Windows 7 x64 and all the PROGRAMS in your computer? 
 
 
 
or
 
 
 
Did you upgrade/update from VISTA 32bit or Windows 7 32bit?
 
 
Best Regards
Freddie

If Sonar loads a file that contains unrecognized midi ports (for instance, if you're changed midi units), it provides you with the unrecognized ports and asks you to supply the new equivalents.

Why can't it do this with VST dll's?

If you use Novation's Automap software (with any of their midi controllers), Sonar will find the Automap version of the VST first and ask if that's the one you want (assuming you didn't use that version when you originally loaded the VST). Isn't it this functionality that just needs extending?

KEv

Have you tried also installing the X1  32bit version.  It doesn't take up a whole lot of extra space and you May be able to access at least some of the settings.

Projects don't care about the path, only Sonar itself cares about that. Project files just "ask" Sonar where they are. I just recently re-organised where all my plug-ins are, and old projects use them just fine.

Have you added the 32 bit paths in Preferences > File > VST Settings?

burkek, not tested it out yet (as I use automap also) as you know it's a wrapper AND adds it's own DLL to every VST you select / use..

but does it deal with 32 / 64 bit properly ? as sure it might be 32 bit versions that are different but maybe with 64 bit, the vst has a different set of identifier also (to make it sem different)