How about, with VST4, the VST manufacturer gets to put a flag to whether the current version of that VST is up to date? Something visible in the GUI. This would save a lot of hunting and pecking.
Ok but what about a “no trust” internet firewall strategy? That only the things that need to connect to the internet is allowed to.
So that the plugin downloader apps update their apps when we run the downloader parent program. As in, periodically, manually. This ends up with being behind in updates, sometimes months behind. But it’s a lot better than everything calling home all the time. What a waste of resources. And a mistrust of what they are sending too. If we could have a look at what data they send then they could be trusted, but we can’t. I don’t even let NI’s services keep running after I am no longer using NI products. There’s no point in running something I’m not using.
Plugin managment with VST3 and Clap support.
So it can be done! However we do not need KVR
Personally, stability is more important than having the latest version in 99% of audio cases. And in pretty much all production cases, updates have to be tested first before being migrated to. Having the plugin itself consume resources to nag at the user to update sounds like something you expect out of Microsoft. And that’s when they don’t do shady things like download and update your machine to Windows 11 if you’re not attentive enough.
1 Like
True. And I get a big dopamine spike when I update a whole bunch of things at once. Efficiency! 
Also I want to be able to choose when I do housekeeping tasks. When I’m in the music groove, problems need to leave me alone and let me cook.