XR18 OSC Example

When I looked into controlling my XR18 via OSC I ran into a couple of roadblocks with the GP architecture. Some of these may have been fixed, I’m not sure

1: GP didn’t support the ‘-’ symbol in an OSC string, and the XR18 uses this quite a lot

2: For some reason GP sends each OSC msg on a random port which changes for each msg sent. This makes it impossible for GP to react to the OSC messages sent back from the XR18 in response to acting on the originating GP OSC msg - The XR18 response message is sent back on the same port where the OSC message originated from, so it means the responses are sent back to random changing ports, which makes it impossible to write a callback.

There is no need for polling, XR18 has quite a sophisticated sub / pub mechanism which can support a number of clients (4 if I remember correctly).

Have a look over this thred

As I say, I don’t know if these issues have been addressed, I think they were added to a (probably immense!) list. I didn’t really get to the bottom of why each OSC msg is sent by GP on a different port, which is the main issue, so if that is needed for some specific reason supporting the XR18 (and other Behringer digital mixers) might be harder than it seems at first glance.