@mr_j
Right now our focus is on finishing IzzyCast. The change to the addressing system isn't coming as a whole right now because it's a big task that will require an overhaul and extensive testing in many areas, but what is coming is the ability to show and hide Controls programmatically. If used cleverly with Gates, Selectors, and Routers you can create multiple "pages" or "tabs" of controls (sort of like TouchOSC). If you build logic to have Gates stop data from flowing to actors whose Controls are hidden, you can theoretically use any Control ID any number of times in your patch (e.g. you could use the Control IDs "100-110" 20 times each in your patch, but if your logic only allows data through the Gates associated with the visible Controls, it doesn't cause any problems). Send in a support ticket using the link in my signature if you'd like the beta build in order to try out this new feature.
The only workaround I can think of right now is to make controls "routable", e.g. have a Popup Menu control that lets you choose which of X different functions changing the Slider control below it will affect.
Here's an example file where this method let me use only 12 Control IDs for 24 parameters: >>>FILE DOWNLOAD<<<
The amount of Control IDs this method saves you increases the more actors to which you are routing data. For example, the routing I set up for the "bypass" inputs on my 7 video actors in that example file only uses 2 Controls IDs (one to select which actor's bypass, and one to turn that bypass on or off) instead of 7 (one for each actor's bypass). This saved me 5 Control IDS working with 7 actors, but if I scaled this up to 60 video actors, I'd still only need to use 2 Control IDs total, (which would save me 58 Control IDs!).
