![]() ![]() Parameters-OSC Routing-Default is set to osc.upd://192.168.0.128:10024, and that seems to be correct. As I see in this specific message, the argument must be an integer. You will want to pay attention to the type of the arguments. ![]() I don't know the dictionary of OSC messages the XR18 accepts, but I would try '/ch/01/mix/on' as you described to see if it is able to act on the mixer. Now that you have properly configured the Target, you might want to create a Routing so that when OSCulator responds to an incoming message, it responds with a OSC event, effectively sending a message to the XR18. UDP seems the correct transport protocol (also the most often used). It looks like the XR18 receives OSC messages on port 10024, so the destination address is :10024. OSCulator doesn't respond to any of this. This tells me that I have the correct address for the mixer. It sends /info to 192.168.0.128:10024, and receives the mixer name and firmware rev.Īnd when X-Air Live Toolbox sends /ch/01/mix/on ,i 1 the channel turns on. When it connects from it's Testing screen, There's an XR18 utility called X-Air Live Toolbox for OSC experimentation. The Macbook OSCulator is running on does. The XR18 does not show up under the Nearby OSC Services pulldown in that screen. OSCulator has OSC input port set to 10024, which is the XR18's port. I have my MIDI Fighter Twister controller listed under Parameters-I/O, and when I turn a knob, OSCulator posts the MIDI CC. Unfortunately, I can't get OSCulator to see my XR18. It looks to me like OSCulator should be able to read a generic MIDI controller and spit out OSC to run any parameter on an X Air mixer over ethernet,Īs well as sending back to update the controller. It can also be controlled by MIDI, but only a very limited subset of parameters. Behringer's XR18 mixer speaks OSC natively.
0 Comments
Leave a Reply. |