clankill3r

Im sending messages over as a single string with osc.

I would like to get the data out of it but so far i have no luck. Either nothing happens, or i get "no such object" or it sends almost the whole string instead of one part.

I don't want the order to matter so instead of "nx: ny:" it should also be possible to use "ny: nx:". Why else use indices.

It looks like this:"nx:0.33 ny:0.21614583 l:0.4453125"

Could someone help?
This is what i have so far:


split-osc-message-and-send-it-away

This sounds like a bad OSC namespace to me. But, if you're stuck with it then this might help:

This sounds like a bad OSC namespace to me.  But, if you're stuck with it then this might help:


I agree with MZED, the OSC addresses don't look right to me. I would expect something more like "/nx 0.33".

If you can change the source messages to conform with the normal OSC structure you can use [OSC-route] external which is available here: 

If you are stuck with the message you posted this will work:

If you can change the source messages to conform with the normal OSC structure you can use [OSC-route] external which is available here: http://cnmat.berkeley.edu/downloads

If you are stuck with the message you posted this will work:


I fixed the OSC namespace, now the message gets sended like this:

How can i route that? Do i need to substitute that as well?

I guess normally you would send it as separate messages but in my case that won't make it easier.

I'm sending data over of multiple objects which could add up to around 200 objects (later i will send the id).

I fixed the OSC namespace, now the message gets sended like this:/ny 0.317708 /l 0.082031

How can i route that? Do i need to substitute that as well?
I guess normally you would send it as separate messages but in my case that won't make it easier.
I'm sending data over of multiple objects which could add up to around 200 objects (later i will send the id).


You need to combine elements of both of the patches you've posted. The [zl iter 2] object breaks up a long message into a number of messages each with two elements. So in your case, you end up with a bunch of messages which include "osc-address osc-value". This is the sort of message that you can pump through the [OSC-route] object.

Now i can finally produce sound!! wheeew :)

Thanks. I almost had that. I only had a regexp : @substitute / inbetween that made it not working.
Now i can finally produce sound!! wheeew :)


Split osc message and send it away