Hello.

I'd like to get an incoming osc message and, after using [oscparse]->[unpack s f], I'd like to be able to take that unpacked symbol, eg.

dmx/light/1/red

and separate it so I can get the values that are separated by forward-slashes, in particularl the '1' and the 'red' so I can use them to route the float value. Is there a way to do this? Or do I need to reformat my OSC message at the source?

@s.elliot.perez The "/" are dropped by [oscparse].
The source format is the root of the problem but....
.... after [oscparse] you could use [route dmx] and [route light] and [route 1] and [route red] and at the outlets of [route 1] and [route red] add back the 1 and the red with messages.
However, because the 1 is a symbol (because it is part of the header) you will need to fix that before using [route 1] like this...... vanilla_bug_oscparse_solution.pd

The OSC format should be dmx/light (header) 1 (float) red (symbol)...... or you will have a lot of work to do in Pd adding back for all the other values..... 2 3 4 5 etc.
[clone] would do it I suppose..... but.....!
David.

@whale-av Thank you! Yeah, it works fine using a bunch of route objects and this can be done in an abstraction using your [loadbang]->[$1]->[makefilename %d] solution, but it'd be hard to do with [clone] since you'd want to send in a list starting with a number into the [clone] before the parsing even happens. And [clone] is nicer than having a bunch of abstractions and manually typing their arguments...

so yeah, I'll probably modify the outgoing osc messages in the future.

@s.elliot.perez If you are always expecting a number encoded as a symbol at that point in the OSC path routing, you could just convert it to a number first.

@jameslo Yes...... I keep forgetting about the new [f] functions.
That will make it easier.
David.

@jameslo @whale-av Thanks for your replies, very helpful. While we're here, how would you approach getting an average of several incoming values for Red, Green and Blue respectively?

What I'm trying below is:

1. route the list twice. Once to put it in one of four groups (so 0-8 go into one group, 9-17 in the next, etc. Then again via the [clone] object. (prepending the same value to the list for 2 routes doesn't seem very elegant)
2. [pack] the RGB values
3. {not pictured} send them to an averager abstraction and set it so that each incoming list's unpacked values go into a [f]->[+] loop to add them, which activates a bang when it's done in order to carry out the division. Do this for each value in each group.

Haven't done up to step three because this seems very arduous and you probably have a better idea.

@s.elliot.perez I don't see anything wrong with having to prepend the leading index twice, I think that's just life in Pd. Just to be sure you know, your cloned abstraction has to receive the red value last, or else the output of pack won't contain RGB values from the same pixel (or whatever it's from).

Edit: Hmm, but if you're using the route to separate them into groups of 9, but then break up the groups again in the clone, then something seems wrong.