But [state] still is useful, and would be even more useful, if it: a) would include the GUIs again and b) would get an outlet that can be used to send state values somewhere else. This way state could be used free of its state-file features and for example just feed a [pool] object.
is there an existing way to to recieve all active sends from a single object? pool's output channeled into a send13 does a fine job of recalling saved settings but is there a similar way to 'feed' it, ie the opposite of maxlib's "remote"...it would probably be a good intermediary solution...