Maybe Izotope would be a better example - every release give you a full set of new plugins but they are 90% the same plugins - Although that situation would be better dealt with by Izotope not pretending they were new
I’m not sure how much of the changes are backwards compatible between different host DAWs - Most VST3 are not running the same SDK build so they don’t need to match ? Do they just ignore the stuff that the host can’t handle ? not sure ?
I’m not trying to be a pain Steve but is it right to have to go through this procedure like in the thread you have just posted? It’s time consuming and completely disruptive to the creative process.
The user shouldn’t have updated his firmware thou.
I’ve been watching what’s happening with the Remote app and every time a minor update is released the remote app gets broken and you are either a programmer and can deal with the script edits or you suffer, the .50 update broke a lot of peoples painstakingly made scripts. And to think we are all going to be forced on to this chaotic new system one day, i have 4 controllers here that are useless with this system but … Im not a programmer.
The thread you posted just shows how much hassle you have to go through to retrieve your controllers
I have a concern about that, I wonder if it is well-founded: I have multiple versions of some programs, PianoTeq for example, and sometimes I’ll choose to use the older version (less demanding on my computer). I wonder if the replacement that occurs would affect that workflow?