Anderton
dcumpian
The real problem comes when you have a suite of plugins that you've organized already, and an update to the plugins causes them to disappear from your carefully crafted custom menu layout. Now, one must determine which plugins need to be added back to the menu because they are no longer there, but not add any that one didn't want to include previously, but not exclude them, because one never knows when it might be useful and can be loaded from the full, non-custom menu anytime to find it.
Okay, I didn't realize that plug-ins changing their CLSID with an update was that common a problem. Generally when I update a plug-in, it stays where I put it; and because the ones I don't use are in an Uncategorized folder, they always have a home too.
I know this isn't what you want, but you might want to know that you can open a .PGL file in a text editor. At first it's just a daunting collection of text, but if you find/replace Name= with a return, then you get a list of all plug-ins in the layout, with the custom name listed first and the original name listed next. You can also replace other text strings with nothing, which cleans it up further. Probably the main value of this is you can see all the VST CLSIDs easily.
Good to know. The suite issue doesn't happen everyday, but it certainly happens once a year or so. Just enough to be depressed about it when it happens, lol. Waves is most guilty of this, though I've had it happen with a few others.
Regards,
Dan