Let’s make this post to collect all the ideas-suggestions-considerations that can be useful to improve the new AMAZING remoting feature, wich allows to write to IOboxes directly from the network via OSC.
Server (vvvv) node gives the OSC tag of the exposed IOboxes.
this tag is auto-generated by the software and it’s related to the pin itself, the position of the IObox into the patches, etc…
Possibility to set a custom OSC address instead of the auto-generated one
I have a module with many parameters, each parameter is exposed over network thanks to ctrl+k and Server node.
if i want to control these ioboxes from external interfaces (that could be placed on a different pc/devices) i’ll need static OSC addresses in order to always address correctly data to every IObox.
There’s a parameters called “quad scale”; would be handy to be able to set a custom OSC address like “/quadScale” for it;
In this way any external interface doesn’t care wich is the automatically generated osc address of that IObox; the external interface just sends a value to “/quadScale” address, and you’ll be sure that even if your patch changes your OSC mapping will be stable.
I suggest also the Server (vvvv) node should outputs other info about the exposed IObox, for example the Descriptive Name and the Tag config pins, but also other informations like min-max and Value Type.
this could be usefull in an open scenario where IOboxes are not just stupid containers that receive wethever it comes but they can also provide informations about the data they contain, data used by interfaces to prepare and send values in correct formats.
Let me know what all of you think guys.