OSC Node

[eamjordan]

Hi,

I am currently testing the OSC Communication in WD with an android QuickOSC app. I followed the procedure below written by Julia written below:
----------------------------------
Network settings in OSC software:
2. enter the IP of your WD computer
3. enter outgoing and incoming port (these port numbers use in WD, outgoing port OSC = incoming port in WD)
4. make sure that in options of OSC software "Accelerometer" is set to Off.

In WD:
5. create OSC input node
6. enter correct connection ID and press [Apply].
7. move a fader, so that in item properties of the OSC node you see the fader ID under "Incoming OSC Message Header", looks like eg: "/Fader/fader1,f".
8. press the button [take], then the FaderID "Fader/fader1,f" is displayed in the text field after "OSC Filter".
9. now press [Apply] again, then the fader data will be shown for "Float1" (depending which kind of fader you use).

----------------------

UDP Communication is working but the "Floats 1-8 and Int 1-8" does not take any value after applying the OSC Filter ( TAKE, APPLY).
If the fader is moved from QuickOSC app the OSC Message header is updateing but the Float values are not.

Any thought?

- Earl

[eamjordan]

Here is the read out:

Incoming OSC Message Header : /seekBar1/0.0.

OSC Filter : /seekBar1/0.0.

[Dennis Kuypers]

Hi,

Just a wild guess, I'm not really into that topic: Is it possible that the WD expects to get a bundle instead of a plain message? Does it work when sending in a bundle?

Best regards
Dennis

[eamjordan]

Hi Dennis, thanks for a quick reply.

The QuickOSC adroid app has toggle buttons, and sliders already made into the user interface template.
The OSC Input Node is receiving all the values and changes from QuickOSC as shown in the "Incoming OSC Message Header"
like for example:

/seekbar1/0.0 from faders
/tog1/1. from toggles
/btn1/1. from buttons.

These are the only values I can get from QuickOSC.

After applying the header in the OSC Filter the OSC Input Node it does not really take the values from the selected filter. After "take" and "apply" of course.

- Earl

[eamjordan]

Can anyone else from tech support share their thoughts about this? Thanks.

[Dennis Kuypers]

Hi,

I don't think that the application complies to the http://opensoundcontrol.org/book/export/html/1 specification. It doesn't include a OSC Type Tag String and it also does not fill up strings with nullbytes. Am I wrong?

Best regards
Dennis

[ricky]

In my experience I only tested Touch OSC application (for iOS and Android) and it works perfectly and it's not so expensive so my suggestion is to try with that.

Cheers!

[eamjordan]

Hi Dennis,

Thanks for your observation. I will check the proper OSC syntax if QuickOSC complies with the standard.

- Earl

[eamjordan]

Hi Ricky,

Thanks for your recommendation. This will be my next move, try it with TouchOSC.

- Earl

[eamjordan]

TouchOSC works well with WD. It has been the wrong OSC syntax that caused the problem with QuickOSC.

Thanks for your support. Cheers!