I like and use that feature of linking “local” widgets to the Global Rackspace, but the more different places you try to do it the more complicated it gets.
For example, these are rackpanels I made for the Lost in the 70’s plugins to demonstrate an external API control surface extension. The colored shading for the two fader banks indicates which one the MCU controller is currently “attached” to. Same for the knob banks. So you can touch a button on the controller to “bank switch” what you’re controlling and the shading follows it.
The more complicated these get, the more of a pain it is to update them everywhere. Especially if it’s just “artistic” stuff like sizes, colors, labels, etc.
I add this to the discussion because in my mind it’s complicated to figure out what’s the “right” approach to managing the “alias” stuff @Keyflow is requesting (which I think is still “Rackpanel aliases” and we’re in the “Feature request” section.)
I think it would be awesome if I could have a “Master B3 Panel” that would automatically update in every Rackspace I placed it into, and I wouldn’t have to rebuild all the widget links to the VSTs like I do with the “save/import” approach.
It’s just not yet clear to me what the best way to manage something like that is, especially when considering the underlying VST might be in the global rackspace (as Keyflow is thinking) or might be in each individual Rackspace.