OSC out ops

[cristianvogel]

I want to format data in a Cables patch as OSC and send via WebSocket through the osc4ws tool I wrote . But I feel I am jumping through hoops with the standard ops, perhaps I am not seeing the right way to do it? Or perhaps we need some OSC out ops to plug into WebSocketSend op?

I'd like to send out data like

      "address" : "/anOscAddress",
      "args" : { {"type" : "f", "value" : 0.5} }
}

or

      "address" : "/anOscAddress",
      "args" : { {"type" : "i", "value" : 5000}, {"type" : "f", "value" : 0.333} }
}

or

      "address" : "/anOscAddress",
      "args" : { "type" : "s", "value" : "some string" }
}

and even blobs

      "address" : "/anOscAddress",
      "args" : { "type" : "b", "value" : "arrayAsBlob" }
}

of course being able to inject changing values where 'value' keys are

[steam0r]

hey,

since all OSC is via websockets anyhow, you could use

https://cables.gl/op/Ops.Net.WebSocket.WebSocketSend

right?

[cristianvogel]

Hi. Yes. Now you can with osc4ws - before you couldn't.
So , what I am asking is to make it easier to create OSC formatted data objects in Cables, before they get sent to the WebSocket. They need to be in a very precise format https://hangar.org/wp-content/uploads/2012/01/The-Open-Sound-Control-1.0-Specification-opensoundcontrol.org_.pdf

Even just a simple OSC message with an address and an array of 1 value, quickly gets hairy.

Usually, you'd be wanting to wire up quite a few of them.

[steam0r]

see other discussion ;) #131