You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature request: provide a way to map RX ports and TX ipAddress:port values to symbols.
In practice, for example, one could associate a symbol like myAudioRenderer to a value like: ipAddress:port
and any OscPropertySenders could accept that symbol and look-up the current value of myAudioRenderer.
Same for OscEventReceiver, which could use a symbol like renderingControl, mapped to a value like: port
The suggestion makes it possible to change ipAddress and port mappings in one location, while making it easier to understand the mapping, since the symbols chosen can reveal where things are coming from or going to.
I implemented a proof of concept example in my forked branch which includes additional components for symbol declaration.
The text was updated successfully, but these errors were encountered:
If I do it in Unity's way, I'll implement an OscEndpoint asset class (inheriting ScriptableObject) that stores an IP address and a UDP port number. You can create OscEndpoint assets on the Project view as many as you like, then you can set them to OscEventReceiver/OscPropertySender properties.
Although there is no plan to implement it soon, I'd like to leave this issue open for future reference.
Feature request: provide a way to map RX ports and TX ipAddress:port values to symbols.
In practice, for example, one could associate a symbol like
myAudioRenderer
to a value like:ipAddress:port
and any OscPropertySenders could accept that symbol and look-up the current value of
myAudioRenderer
.Same for OscEventReceiver, which could use a symbol like
renderingControl
, mapped to a value like:port
The suggestion makes it possible to change ipAddress and port mappings in one location, while making it easier to understand the mapping, since the symbols chosen can reveal where things are coming from or going to.
I implemented a proof of concept example in my forked branch which includes additional components for symbol declaration.
The text was updated successfully, but these errors were encountered: