Remapping old plugins in old projects to newer version of the plugin when reopened (X2)

This is an ongoing issue I've had with Sonar over the years and maybe they fixed it in X3, but its still haunting me in X2. Often if I open an old project from a previous OS/Sonar installation in Sonar it will consider some of my VSTs as missing despite there being versions of these VSTs installed. I realize there are many factors that can cause Sonar not to recognize the installed VST as the same as the older one (though in my case they are sometimes the same version).
 
Is there perhaps a way to find out the ID and file path associated with a missing plugin to help troubleshoot why it thinks its missing?
 
Is there still no way to make Sonar take the settings from the missing VST and apply them to the installed working VST if they are basically the same?
 
Thanks.

For me this is just bad plugin design.
i.e. Rapture and Dimension LE vs the full versions, really we should be using the same DLL's just different serial numbers rather than a different codebase, can't do much though from 32 bit to 64 bit.

I don't know how Sonar stores the vst data for a project, but I would think that you could remap the values from the missing vst to the new vst, a sort of "At Your Own Risk" function.

scook

CakeAlexS
For me this is just bad plugin design.
i.e. Rapture and Dimension LE vs the full versions, really we should be using the same DLL's just different serial numbers rather than a different codebase, can't do much though from 32 bit to 64 bit.

If the LE and full versions were not different plug-ins then those using the LE version to save CPU when necessary would loose the ability to switch between versions.

I'm not sure I understand this. The point is you use the same code version so you don't need to switch between versions. If you design it well enough you would just have certain features locked or unlocked depending on the serial number, features not being used will not take up any extra CPU.,.. Melodyne does this for example.... 

CakeAlexS

scook

CakeAlexS
For me this is just bad plugin design.
i.e. Rapture and Dimension LE vs the full versions, really we should be using the same DLL's just different serial numbers rather than a different codebase, can't do much though from 32 bit to 64 bit.

If the LE and full versions were not different plug-ins then those using the LE version to save CPU when necessary would loose the ability to switch between versions.

I'm not sure I understand this. The point is you use the same code version so you don't need to switch between versions. If you design it well enough you would just have certain features locked or unlocked depending on the serial number, features not being used will not take up any extra CPU.,.. Melodyne does this for example.... 

Anti-piracy measure probably.

fallenturtle
This is an ongoing issue I've had with Sonar over the years and maybe they fixed it in X3, but its still haunting me in X2. Often if I open an old project from a previous OS/Sonar installation in Sonar it will consider some of my VSTs as missing despite there being versions of these VSTs installed. I realize there are many factors that can cause Sonar not to recognize the installed VST as the same as the older one (though in my case they are sometimes the same version).
 
Is there perhaps a way to find out the ID and file path associated with a missing plugin to help troubleshoot why it thinks its missing?
 
Is there still no way to make Sonar take the settings from the missing VST and apply them to the installed working VST if they are basically the same?
 
Thanks.

I have this same problem and it drives me crazy! From what I can tell, they change the CLSID numbers on the plug in the version changes. Therefore, (here's a perfect example and one that makes me want to choke someone) if you have an old Sonar project with say an older version of the PSP Stereo Enhancer. Install the new one and all of your old Sonar projects will tell you it's not installed. To make matters worse, they reversed the controls of the freakin' plugs so your old plug saves via VST Sonar window are useless! Luckily, I had the old versions still installed on my real recording pc so I was able to write down my custom plug settings and transfer them to the new plugs via screenshot.
 
But the whole "missing plug" thing is a nightmare. It almost forces you to leave every plug and DAW on your machine in order to play these projects back without any issues. Here's my best advice to you...
 
1. At the end of EVERY project you create and save, put the Sonar version on there at all times so you know for sure which version it was authored in. So, when you name the song, you name it "Name of Song X3.cwp or .cwb.
 
2. If you have any older computers with old versions of Sonars plus the old plugs, keep them just in case you find an old project really needs to be dealt with and seen for what it is. I have several pc's here with operating systems running Win 95, Win 98 SE, 2000, XP, Vista and Win 7 with running versions of Cakewalk/Sonar from pro audio 9, Sonar 2, Sonar 5-8.5 and X1,2,3. So in the event I need something open, I got quite a bit to choose from to either retrace my steps or copy things. I know this is total over-kill and not a necessity for everyone, but most of the time, you're not going to get much for any old pc you have. As long as it works and you have the space, keep it for dumb stuff like this. Just 6 months ago, I went into Cake pro audio 9 to grab an old project that I needed.
 
3. When updating plugins, if you have another pc or some sort of test box, try the plug update on that one first. What you can do is, go into plugin manager and look up the plug CLSID and write it down so you can compare the updated plug with the old one. If the numbers are different, uninstalling the old plug will give you the "not installed" message. 
 
4. 8 times out of 10, unless a plug (like Waves or something, who have consistent CLSID's) has a major update, leave the old one on alone. Most times when I update a plug, I ask why I spent the money because it's just abotu never worth it unless I'm having issues. This PSP issue I'm getting is my fault. I knew I didn't need the new updated plugs because I was perfectly happy with the old ones, BUT....the old ones were not 64 bit and I have been on a quest to make Sonar 64 run as smooth as possible. In doing this, I have since removed every possible 32 bit plug and Sonar 64 has performed perfectly for me. I just need to get Drumagog 64 and I'll be set.
 
I know none of this is really helpful to you, but it's what I've done to sort of control the problem. When a vendor changes a plug ID number, there's nothing that can be done unless someone makes some sort of software that takes the plug ID and corrects it. but to Sonar and other DAWS, the new ID signifies a new plug. Therefore, when you uninstall the old one, the system sees it as "gone".
 
I could be totally wrong in everything I've said here....but I think I'm close as to how this may work. I don't know if it's the CLSID number...but I know that number is what identifies plugins. But there could be something in the code that is messing with things as well. I'm just sharing what I THINK may be the problem as well as what I've done to sort of prepare for it. Just test on another machine if you can and write down the CLSID's and compare them.
 
-Danny

An XML mapping file sounds like a good idea.