send OSC messages in/out of RNBO
Would it be possible to send OSC messages (and customize their osc tags) out of rnbo to another location than your host device. By instance another application on the target Raspberry Pi listening to a port number or even another computer with another IP address? ...Thanks a bunch
I found a way to create listener ports for sending and receiving OSC messages on the Runner == /rnbo/listeners/add 192.168.1.80:8003 == though still wanting to customize the OSC tags
FEEDE,
Glad you found the listener setup.
As far as custom OSC tags, the closest thing we have right now is outports. You can customize your outport address suffix with the outport name [outport /my/path/name] but the runner will add the /rnbo/inst/0/messages/out prefix and only allows for floats, float lists, or no arguments at this point.
Indeed I noticed thats how it's currently done. Maybe for a future release the inspector window could reveal a field in which you can customize the address suffix.
https://fb.watch/hguvjBlWwW/
FEDDE,
I don't know what you mean by "inspector window could reveal..." can you elaborate?
What I mean is that within the current osc tagging logic, the osc tags for the in- and outport's are following the data structure of rnbo. It would be handy to have the possibility to bypass that and fill in a custom (more direct and client / server specific osc tag). I would use the in- and outport's inspector for that like you did with the Metadata field...
But it's just a practical issue that comes about when junctioning stuff with OSC. A better way would be to be able to address and define the gpio's directly from within a custom scripting environment inside rnbo. As to define in and output as gpio's. By instance in a case where you want to sample the inputs of an mpc3008 ADC directly into an [in~ 1 2 3 4 5 6 7 8]. In this way you dont lose accuracy and increase workflow...