Corbin White

I've been using OSC-route to create an OSC API. I'd like to use an OSC string something like /set/channel/[n]/pan, with [n] being any number between 0-71. It would obviously be quite laborious and inefficient to specify each possible number with /0 /1 /2 /3 ... /71, but there doesn't seem to be a way to route a range of address strings with OSC-route. Have I missed it? Or is there a more appropriate method?

Hi all,
I've been using OSC-route to create an OSC API. I'd like to use an OSC string something like /set/channel/[n]/pan, with [n] being an

osc-route-wild-card-sub-addresses

I presume that [OSC-route] is included in an additional package that you are using that I'm not familiar with. However, it probably works the same as [o.route] from the ODot package. I'd suggest using [fromsymbol @separator /] and [unjoin] objects to separate the parts of the OSC message thus:

image.png

 used with a wildcard is quite a good way to put an index back into an OSC message:

And in case you were wondering, sprintf used with a wildcard is quite a good way to put an index back into an OSC message:

Thanks Andy! Can’t believe I didn’t just slap a message onto the [OSC-route] output, probably would‘ve figured this out. Anyway, works just as you said, and now I know about [unjoin] and using @separator.

Thanks Andy! Can’t believe I didn’t just slap a message onto the [OSC-route] output, probably would‘ve figured this out.  Anyway, works just as you said, and now I know about [unjoin] and using @separator.

OSC-route wild card sub-addresses