Standalone OSC Extension

[wirmachenbunt]

not working here, or is this still not ready to test ?

[steam0r]

can you try this in nightly build? https://github.com/cables-gl/cables_electron/releases

thanks!

[wirmachenbunt]

yes, the ops show up in nightly but i can not receive nor send data from and to cables in combination with vvvv. i tried different ways. there seems to be a connection and the cables in cables show activity but the messages can not be interpreted

what software do you use to test the OSC messages with cables ?

[wirmachenbunt]

there is some data when i inspect to osc op message

[steam0r]

OscNumer is the webosc extension, Osc is the standalone native thingie...it's confusing but the standalone extension only uses osc and oscsend...maybe the other osc ops should be compatible at least in working with "messages"

[wirmachenbunt]

i tried all ops to receive or send OSC data, from and to vvvv. nothing works right now. i'll investigate further, because there is something going on in terms of traffic, just no workable output on both sides

[steam0r]

this looks "workable", doesnt it?

use ObjectGetArray and then work your way down from there

[wirmachenbunt]

true, it might be confusing because there are two OSC solutions in cables standalone ? the one in the screenshot at least shows one osc channel, but if there are more than one (which is the point of OSC), only one is showing up.

i tested this with old and new vvvv, old vvvv correctly sees all the OSC channels while cables just shows the last channel.

again, how do you test this implementation in cables, i ask because maybe vvvv is doing something funky and cables has problems understanding it

[steam0r]

channel is "per message", so you definitely only ever see the last one and have to handle receiving these in arbitrary order. try vizlogger so see all of these messages.

i agree that its confusing these other osc ops do not reall work well with these

[wirmachenbunt]

yes, there are things in the vizloggger, thanks for this hint. but why is message not working.

re-reading you comment above, yes, we need ops to understand OSC messages or the whole OSC stuff in cables makes no sense

[steam0r]

OscMessage thinks the message hast the address in "a", your messages have the address in "address":

outAdd.set(msg.a);
outNum.set(msg.a.length);
outArr.set(msg.v);

i know basically nothing about the OSC protocol so i do not know which is "right"

[wirmachenbunt]

not sure what "a" is ? a OSC message is from the user perspective simple, you have an address (aka channel) and via this, comes data. either a single value (most of the time) or more complex stuff like an array

so what you see in the vizlogger makes total sense, adresses are always written like that "/nameofchannnel", followed by data (args).

i look into that oscmessage op