View Single Post
Old 11-12-2017, 01:11 AM   #12
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,690
Default

I suppose a major problem is that

- "@output OSC ..." assigns a random port number as a sender address to the sending USP socket to be used with oscwrite().
- the hardware device (XR18, but supposedly close to any other, as well) will send messages back to that port number.
- with "@input OSC ..." the port number the receiving UDP socket is opened to listen on (not "to") needs to be given, and this number is not known to the programmer. To allow this the ID of the corresponding output port would be needed to be given in the @input command. Easily doable, but seemingly not implemented in the current version of OSCIIbot.

Seemingly when attaching to Reaper via OSC, Reaper can be set to send OSC messages to a predefined port, and same can be used in "@input OSC ...". But hardware devices just use the port given as sender in the received messages they are controlled by.


Pls see my message to Justin in the developers forum.

Did you really succeed in requesting data from an X32 with OSCIIbot ?

-Michael

Last edited by mschnell; 11-12-2017 at 04:19 AM.
mschnell is online now   Reply With Quote