Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ip/port mapping to symbol feature #27

Closed
zacksettel opened this issue Feb 23, 2021 · 3 comments
Closed

Add ip/port mapping to symbol feature #27

zacksettel opened this issue Feb 23, 2021 · 3 comments
Assignees

Comments

@zacksettel
Copy link

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.

@keijiro keijiro self-assigned this Feb 24, 2021
@keijiro
Copy link
Owner

keijiro commented Feb 24, 2021

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.

@keijiro
Copy link
Owner

keijiro commented Apr 25, 2022

I introduced OSCConnection class in v2.0.0 to solve this problem.

@keijiro keijiro closed this as completed Apr 25, 2022
@zacksettel
Copy link
Author

zacksettel commented Apr 25, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants