Program Change - Preset Number Info on Event List.

[carlo]

Hello friends, I would like to know if there is any way to locate the preset number chosen in a specific VST that is not installed on the machine? For example: I have the Predator 3 plugin installed, and the old project refers to the old Predator 2! Is there any way to view the Program Change number in the MIDI track events? I've already looked in the Event List, but there's nothing related to the Preset number, only note information! I have many old projects that I need to finish, and some older VSTs are not on the machine because they were replaced by newer versions. Thank you.

[Amberwolf]

If you didn't use bank/patch changes, and didn't save the preset separately from the project as an FXB or FXB file to manually load into the plugin, then the preset data is simply part of the project data that would be fed into the plugin itself directly and isn't user accessible.  If the plugin isn't installed, and you just get the "missing plugin" dialog for it, the preset info is not sent anywhere becuse there's nowhere to send it. 

If the new version of the plugin is so badly designed that it doesn't understand or accept data intended for it's previous versions, then that data is "lost", in that there is nowhere for you to retrieve it from. 

To get that data back you'd have to install the old version of the plugin that the data was intended for/came from, and load the version of the project that still asked for it (hasn't yet been replaced by the new one).   

 

Then you could try saving the state as an FXP (preset) or FXB (bank) and then see if that data will still load into the new version of the plugin.  My guess is it will not, because that's the same data Sonar would be sending it anyway so if it is not accepting it now it probably won't then either.   

At that point, you would have to manually recreate your preset by taking screenshots of all the controls in all the various parts of the plugin with the old version, and then try to figure out what those correspond to in the new version, and set those controls the same way.  It will probably still not sound the same if they've really changed it that much to not accept the old data, though. 

 

 

 

[Xoo]

Sometimes the preset name is visible too if you open the cwp file in a tezt editor.

Edited 2 hours ago by Xoo

[David Baay]

1 hour ago, Amberwolf said:

If the new version of the plugin is so badly designed that it doesn't understand or accept data intended for it's previous versions...

I think it's pretty standard in the industry to give new versions of synths a new plugin UID. This helps distinguish them and keeps the sound of an existing project from changing when the sound of the new version changes. But this also means that the DAW has no way of recognizing that they're essentially the same and doing an automatic substitution when you do want that.

For the OP's situation (which most of us have probably encountered at one time or another) it would be nice if Sonar provided an option with Replace Synth that tried to apply the patch parameters from the replaced synth to the new one, but this could get tricky if the synth paremeters are no longer the same or a user tries to do it with completely unrelated synths.

As an example, Pianoteq tends to change its sound pretty dramatically with every major release, so you wouldn't want an automatic substitution to happen in a finished mix. The one time they made a big change in sound with a minor release (8.3) and no change in UID, they ended up having to provide users a way of loading the original v8.0 sounds to address this.

[Bass Guitar]

Another example was Addictive Drums. When they released the VST 3 version none of my presets showed. I have at least 30. It  was blank. 

But it did seem to load up projects  with all the correct settings and kit pieces. 
 

I had to manually re save them which was becoming a PITB so I just reverted back to the VST 2 version. 
 

Last night I upgraded to the paid version of Steven Slate drums for only $50 Black Friday deals. I’ve lost interest in Addictive Drums. 
 

 this situation the OP is in has happened a few times to me so I am in the habit of freezing all my synths and using save as to store them in a safe place. That’s the way to make sure your sounds are  future proof. 
Ad then keep the old version installed and what you can do is put it on the excluded list. Then if you open a project that used it just re include it.