I'm trying to route Monome-like grid data from OSC, so I'd like to cascade [route] to process lists from OSC until I get to the last number, which will ultimately be used for note on / off messages.

To start, I'd like to see if I can do everything I can with Pd Vanilla.

I'm coming from MaxMSP so I think the trouble I'm having might stem from that.

I'm using:

[netreceive -u -b 8024] --> [osc parse] --> [list trim]

But when I route the result through a [route 1], I don't get any output.

Any ideas?

@waveplant Hello
When you route a list through [route 1} then a list that starts with "1" will appear at the left outlet, and a list that starts with 2 (or anything else but 1) will appear at the "rejection outlet on the right. In both cases the first symbol (1,2 whatever) will have been stripped away.
If you feed (for example) "lala dog 4" to [route lala] then you will get "dog 4" from the left outlet.... so it can work with symbols too...
David.

Hi David,

Thanks for the reply. What you're describing sounds like Route's normal behavior, but there's something strange going on with the parsing when the list is coming through [osc parse].

See this thread:

http://lists.puredata.info/pipermail/pd-list/2014-10/108189.html

I can't quite make sense of the workaround because I wasn't subscribed back then and didn't have access to the attachments.

-Joel

@waveplant I don't have [oscparse] available help me understand (win7 PDext0.43), but I assume it spits out the symbol list with the forward slashes removed.
The discussion in your link is all about converting symbols to floats (and back again) and the conclusion (it's a long thread) is that oscparse should do as expected and output a symbol list.

So, maybe, if you do not trim the list with [list trim], you could use [list split] (and a whole chain of them if necessary) to get at your list components.
Not a elegant as [route] maybe, but [list] is not symbol/float sensitive.
David.