For a kind of silly reason we have to change the name of a published Plugin, but it is what it is.
Although the Plugin name changed, we want the instances in old DAW projects of our customers to be associated with the new binaries.
Plugin Shortcode and vendor etc. will be the same.
Did anybody try to do this before?
Are there hosts or formats (VST3, AU, AAX) that could cause trouble from your experience?
I was in this situation, but decided that its better to make the newly named plugin a new plugin, because no matter what happens you will get support requests from folks who are confused by the name change, and if you just give the new-name a new-bundleId, folks can still load their old projects and use the new plugin. Just look at it as an opportunity to add new features, though …
Years ago I did this the only DAW that caused an issue for us at the time, and because of it we had to revert the change, was WaveLab, for one reason or another it ignored the plugin code and used the plugin filename on disk! That being said things have probably changed since then and that may be close to 10 years ago.
For anybody else running into this issue:
Seems like Ableton is having the same problem as Wavelab, and if your plugin has ARA Reaper is having trouble as well, so we will go with the new bundle id approach.
And all that just because native english speakers confuse GainAimPro with ga* name Pro too often, should have realised this earlier…
This was mainly for VST2 in WaveLab; their VST3 implmentation seems to be sensible. But don’t hold me to that statement…
Also watch out of MAGIX DAWs which use the name on disk for VST3 and will break session compatibility if the name changes.
