Hi,
 
I've just upgraded to Sonar X3 Producer, and I'm having trouble opening projects created in Sonar 4.  Seems that audio files work fine, but I'm getting a Missing Plug-Ins warning (Kontakt, Waves, Dreamstation, etc.).  I've added appropriate folders to the VST Scan Paths, but just can't get things to work.
I'm hoping someone out there may know what's going on....would like to move on from troubleshooting to making music.
 
Thanks!
 
-Brian

Well....guess I just found that I could delete and reload the synths, then reroute the midi channels.  A bit of a pain, but at least I can move forward.

Here is a snippet from Noel, from another ancient thread:
 
"Projects saved in either the 32 or 64 bit version of SONAR should open fine in each other. The plugins ID should be identical on both unless the vendor specifically coded them not to be. 
Normally opening a project saved with an older version of a plugin should load the new plugin automatically. SONAR tolerates minor changes in the plugin file name, (if there is a conflict you will get a dialog asking you to choose the plugin) but if the vendor changes the VST ID for the new version it will show up as missing."
 
From the above, I wonder if the VST ID's for the plugins are now different than they were.  If so, I would wonder if this is due to a change by the plugin vendor due to perhaps the vendor creating a new VST ID as a result of releasing a 64-bit version of the plugin.
 
I no longer have 3rd-party 32-bit plugins on my computer, so I cannot compare VST ID's between Kontakt 5 x32 and x64.
 
Bob Bone
 

So, for the above post by me to apply, it would suggest that your VST scan paths are pointing at physically different instances of these plugins.  Is that possible?
 
Bob Bone
 
 

Its likely the old plugins were DX and the reason Sonar is not seeing them is its looking for DX plugins that are 64 bits if X3 is also 64 bits. 

Thanks!  Useful information here.  I will continue to explore....

SONAR 4 was released almost 10 years ago. Its not surprising to me at plugins referenced by those projects fail to load. Do you still have SONAR 4 installed on your machine and do the projects load with plugins intact inside SONAR 4?
If they do load within SONAR 4 that means that the plugins do exist on your machine. If not then you do not have the same versions of the plugins installed any more and will have to manually insert alternative versions. If the projects used VST plugins, SONAR 4 used a vst wrapper at the time. However X3 should generally still be able to load the plugin to the project, provided the plugins in question actually exist on your system in the VST scan path that X3 is using.

Noel what would be fantastic would be the ability to extract preset info for plugins. I've had versions of various NI, Cake (Pentagon!!!), and some a few misc (GURU for one) plugins that simply will not be recognized by a newer version of SONAR on a DAW rebuild. I posted a gillion times about it and it sidelined me for almost two years worth of troubleshooting before I finally gave up and recreated presets from scratch. This has come up many times...granted it's not a shiny new bell or whistle but it's part of comprehensive asset mgmt and would be very handy for folks that are in it for the long haul.

@wicked - that's a great idea.  Maybe you can submit a Feature Request for this.
 
Bob Bone
 

...wicked
Noel what would be fantastic would be the ability to extract preset info for plugins. I've had versions of various NI, Cake (Pentagon!!!), and some a few misc (GURU for one) plugins that simply will not be recognized by a newer version of SONAR on a DAW rebuild. I posted a gillion times about it and it sidelined me for almost two years worth of troubleshooting before I finally gave up and recreated presets from scratch. This has come up many times...granted it's not a shiny new bell or whistle but it's part of comprehensive asset mgmt and would be very handy for folks that are in it for the long haul.

As mentioned if the plugin is not located or we don't find something with the same signature then we load a proxy plugin instead of it.
Technically the preset is still intact since the proxy retains it in the project but until you have the plugin that can load the preset installed SONAR won't see it.