Noel Borthwick [Cakewalk]
I'm curious what tasks you perform in plugin manager and why it's important to you. It's a tool that one normally only uses to create new layouts.
If you had 2000+ plugins you'd be running the manager a lot more often too. Seriously though, a great number of plugins have issues with VST3, which require disabling the VST3 version. It's also fairly common for updates to have issues and require figuring out why a plugin isn't showing up inside Sonar - while the plugin manager is weak it's still faster than regedit. I also have to rename a number of NI plugins since there is no way to tell which version is which with some of the Kontakt plugins. Sonar loves to lose the renames so I end up with 3 copies of Kontakt 5 instead of the more detailed name with the number of output channels.
The layout controls I would use all the time if they scaled up to handle the number of plugins I have. I bought the MenuMagic app to try and help, but it's not really up to handling that many plugins either.
Recent releases of Sonar have also begun doing a crazy enumerating all my plugin registry entries the first time I right click on a audio or MIDI clip. At first I thought Sonar was hung, eventually it finishes walking the entire registry and brings up the right click menu. Only does it the first time after Sonar is started. I think this "feature" was added around January. Not sure it's 100% related to the Plugin Manager but it is really annoying. Only figured out it was plugin scanning because I ran Sysinternals Procmon and watched it enumerate every single plugin on the first right click on a clip.
I still have DX 32-bit plugins (using a 32-64 wrapper) that I bought in the 90's installed and working. I pretty much refuse to give up any software lightly. I get the impression no one at Cakewalk has ever used Sonar with more than a few dozen plugins.