Does X1 Fix This? Noel, or anyone?

This is a problem with migration. Many old songs with 32 bit versions of plugins can't be opened properly. You open and the
plug-in isn't found, so it tells you this. But you're still screwed. There should be a 'BROWSE' button you can click, to find that
new .dll location and have it look there for that in the future. Then when done that plug-in loads WITH the settings it had in
the older 32 bit machine. It doesn't do this. It makes it impossible to have a true archive going forward should people want
to open a bundle, tweak and bounce it out again. Sure, you can apply the effects or freeze tracks to renders a much larger
bundle, but you lose the ability to go in and tweak doing this. You can re-load the plug-in to the track or bus it was on, but
the settings of course will not be there. Even if you move plug-in presets from your old presets folder to the new folder for
them in your new install, you can't open those presets. Even if you could, not all plug-ins are using presets. You may have
settings only used in that one particular song. You'll start from scratch. Other platforms don't appear to have this issue for
users migrating from 32 to 64 bit, or a different OS or computer. That move from 32 / XP to 64 / Vista or to Win 7 has been
going on for a while and it's the future and inevitable for most people. Isn't this frustrating to any other Sonar users here?

Mark D. - I plan on upgrading to 64bit in the future.  I'll be interested to see people's responses and if you are able to get this to work.  It would be a major hassle if we have to recreate plug-in settings just because we move to 64 bit.  I hope you can get this to work.

I have this very same exact problem and it really sucks.

I hope X1 does this better.

there should be a much more streamlined way to "replace" plugs, like how amazingly easy it was in Project 5, IN THE SYNTH RACK!!!!!

Brandon Ryan [Cakewalk
]

Replace synth will hopefully find it's way into SONAR before too long.

That's exactly what I'm looking for! Excellent news! Now I can't wait for X1 and for X1 patch 1

Brandon Ryan [Cakewalk
]

Just to be clear, SONAR X1 does not currently have Project5-like "replace synth" function but it is something we plan to implement at some point down the road (hopefully not too far down the road).

Just messin' with ya Brandon! Good things come to those who wait

benstat

Brandon Ryan [Cakewalk
]

Just to be clear, SONAR X1 does not currently have Project5-like "replace synth" function but it is something we plan to implement at some point down the road (hopefully not too far down the road).

Just messin' with ya Brandon! Good things come to those who wait

Ha - cool. Just didn't want to disappoint anyone.

bitflipper


I've always wondered why the plugin manager doesn't have a button labeled "Add Plugin". It's annoying to have to rescan everything just to add one new VST.

+1. Great idea!

I open songs that were created in 32-bit SONAR in x64 SONAR all the time and as long as the plugin has an x64 version or it's a 32-bit vst I don't have any problem. I'm not sure why you'd need to browse for a .dll.
If you have a 64 bit version installed, it may not always open if the 32 bit version was in the old system. As suggested, I DO have all of my plug-ins in one simple folder, and the scanner points at it. Again, this is NOT a problem with being unable to open a plug in. Every plug-in that I wanted to install installed correctly. I can open a new project and load them all. BUT if that plug-in was in the old bundle from the old system, either becuase Sonar expects the .dll to be in the same folder in the same old computer (and not the new one) or perhaps because it was 32 bit then and is 64 bit now, the plug in doesn't load.

Hence, the need for one to 'browse' to find it, and tell Sonar 'whenever you look for this plug-in in the future on old Bundles, here's where to look', so you fix it once, for good. Further, if Sonar could do that automatically, ie. finding the 'nearest match' (ie. the newly installed .dll on the new machine for the plug-in that it at first doesn't find when looking for that in an old bundle from an old machine you are opening) and give you the ability to acknowledge (ie. 'yes' a button to say that's the right one) that would work too. Though Browse would be simpler. It probably wouldn't be much work to add this feature on "X2".

Well things are better now than they used to be. I forgot which version, but a few years ago if you were to open a project and some plugins were missing, then save the project, you would never get those plugins back (at least not their state). They would be completely removed out of the project.

Then CW changed how Sonar works and if you now open a song and there is a missing plugin, even if you then save the project, it puts a plugin placeholder that temporarily keeps the old plugin's state. So if you then find the old plugin again, do a rescan and re-open the project, the plugin will be loaded properly with it's original state.

If I remember correctly Rapture and Dim Pro were updated recently and the x64 versions  are named differently to the 32bit versions...

THis of course was a pain when flipping  from 32bit to 64bit and back!