If i use an OSC monitor on the port 9001 It picks up the commands im sending when i move a fader and it also picks up the feedback from onyx when i move a fader in onyx. However the two programs are not communicating and moving a fader in one doesnt affect the other.
I am not the aforementioned official technical support, however I do work with OSC quite often.
I do not believe OSC will operate within the same device the way you have setup.
The only thing I can think of would be to setup a loopback network address (usually 127.0.0.0) and see if Onyx and your other software will recognize it.
What you are currently doing is telling Onyx to look at your Wifi card, however the OSC signal isn’t coming from there, its coming from another internal software.
I think he meant that you have to install the KM-Loopback adapter driver. For some reason Onyx won’t use 127.0.0.0 as the loopback. So it’s necessary to have the virtual driver from Microsoft installed, which is also necessary for Artnet & SACN loopback. Onyx will automatically configure the virtual network adapter in settings if you wish.
I’ve tried two separate computers to test it’s not the loopback causing problems.
I am sending OSC from one to the other over a Wi-Fi network, I have OSC Monitors on both showing what they are sending and receiving and that is all good. I think it must be something I’m not setting up correctly with Onyx at the moment the device space is 001 but i’ve also tried 001 and the input IP address is the IP address of the laptop sending OSC and on that laptop the outgoing IP is set to the address of the Onyx PC. Any Ideas?
Actually when I move a fader in Onyx I am getting OSC feedback so the connection seems to be fine, maybe it’s the OSC commands that I am sending.
I tried sending /1/Programmer/fader5 which I found by using the touch OSC editor and seeing what the first fader on the Onyx Layout was sending.
I’ve also tried /Mx/fader/4203 because that is the address that is moving in the OSC monitor when I move a fader within Onyx?
Perhaps the release preview …48 has fixed this problem which has been reported in another thread. Search for TouchOSC and you will find it. I suggest trying the preview.