Why doesn't Reaper use plugin ID's?
I recently updated all of my Universal Audio plugins and noticed they made a new version of the SSL E Channel Strip. Whenever they make a new version of a plugin, they retitle the file name of the original plugin to ________ Legacy.dll, so this particular plugin became UAD SSL E Channel Strip Legacy.dll. The new version of the plugin takes the original name (UAD SSL E Channel Strip.dll). This means when I open old sessions where I used this plugin, it pulls up a fresh instance of the new version of the plugin and doesn't recall my saved settings.
To solve this issue, I renamed the legacy file back to its original name and gave the new version a different name. Now the old plugin loads with all of my previous settings. I contacted UAD about this issue to find out if there's a better way to go about it, and they said this is my only option because Reaper is not on their list of approved DAWs since Reaper doesn't use plugin ID's.
Besides the fact that it's a hassle to stay aware of when plugins become legacy versions and rename the files whenever this happens, they informed me that any manually renamed files will no longer receive updates unless I change them back to their proper names.
I've never had this problem with any other plugins or companies, so I do think it's dumb that UAD does it this way, but at the same time I don't understand why Reaper doesn't use plugin ID's. Aren't they there for that reason? Assuming there's no good reason not to use the ID's, is it possible to implement this in the future?
|