alistair macdonald

I'm using the Lemur app on an iPad. As I make more complex interfaces, the OSC receiving bit of my Max patches gets very messy.

What I'd like to do is to split the incoming osc messages such as

/BCtrl/k1/x /BCtrl/k2/x /BCtrl/k3/x /BCtrl/k4/x

after /BCtrl so my route object looks like

(that's a simple example, some osc messages are much longer)

this would make the route object shorter & save me lots of typing

But I can't find a way of splitting the message at an arbitrary /

I'm using the Lemur app on an iPad. As I make more complex interfaces, the OSC receiving bit of my Max patches gets very messy. 

What I'd like to do is to split the incoming osc messages such as
/BCtrl/k1/x /BCtrl/k2/x /BCtrl/k3/x /BCtrl/k4/x
after /BCtrl so my route object looks like
 [route /k1/x /k2/x /k3/x /k4/x]

(that's a simple example, some osc messages are much longer)
this would make the route object shorter & save me lots of typing

osc-message-routing-splitting

What about cnmat's OSC-route?
You could first parse your message with OSC-route /BCtrlL ... then parse the remaining result.

osc message routing & splitting