So Noel, please clarify - is the name of the preset displayed in situations where the proxy is in place due to the plugin not being found?  
 
Bob Bone
 

Good question, Bob... if the preset name were available you could perhaps replace with a newer version/changed GUID and still get similar results.   Hypothetically.
 

Noel, can you elaborate on "proxy plugin"? I don't understand that. It seems like it would be quite useless since the "Replace Synth" command doesn't try and pull the preset info when it loads. This has also proven to be quite troublesome because I can get a proper real updated version of a plugin to load fine but SONAR won't recognize it as the same one that's already loaded in a project. Thus, the preset it still lost. If that data still exists and is present in the project file, it would be fantastic to capture and be able to export it, even as a generic VST preset that we can manually open instead. We're not talking even simple synth sounds keep in mind, but these can represent complex sampler presets...which if unable to be recovered could totally kill a track. (hip hop guys back me up here!)
 

And let me add, I'm sure that since this a rare occurrence and only to long-time users of a program, I understand that this might be hard to justify from the point of view of development resources (ie, man hours). But let me add that this is marketing gold, because EVERYONE who uses complex software like this loses data or has crashes that can torpedo a project file. A bullet point on a feature list from a new version that says "make music and stop being a file clerk. Our new asset tools allow you to find data and protect your work so you can spend less time troubleshooting and more time making music!" would win hearts and move units. :-)
 
 

Its generally quite meaningless to try and load a preset from one plugin to another which is why replace synth does nothing with the saved info. Attempting to load one plugins data to another will either fail or crash that plugin. Even if its a different version of the same plugin its unlikely to work if the plugin ID was intentionally changed by the vendor.
 
The "proxy" is the placeholder missing plugin that SONAR uses when loading projets that contain missing plugins.

I was just thinking it might help to know the name of the unloadable preset, not for trying to actually use it, but just to have an idea of what it is so that a suitable replacement could be located and then used with some replacement synth.
 
The track name might just say 'Bass', but knowing that the preset that was loaded for that track was 'Scarbee Pre-Bass - Amped - Fat', would give me a good idea of what to look for in an alternate bass sound preset.
 
So, I would think this kind of information - since it is preserved somewhere in the project file (I hope), would be helpful.
 
Bob Bone
 

Yeah, that's what I was thinking too, Bob.   And for an updated version of the same plugin, the preset name could be enough to restore the desired output.   Code-wise, of course, I'd no idea what it would take. 
 

Yes to all of this. That data is still the missing link for reviving projects from the dead or near-death. Even if we just able to read the preset info in a useful way it could save our butts big time.
 

Well, in general terms, they are already building a message box to post the fact that the plugin is missing, and to the best of my knowledge that preset info is stored within the project, so I would GUESS it would mean appending the preset name to the 'missing' message.
 
IF the above is correct, then I would not think it very involved to add, but I have no idea how they constructed the section of code that generates the plugin missing message.
 
In any case, I DO think it would be helpful to have that info presented, in that situation.
 
Bob Bone
 

Yes I would agree here also. Some way to read the name of the saved preset in the saved project.