You can use wild cards like [routeOSC /*/*/noteon ] or use a [set
/x/y/z( message to dynamically set [routeOSC]'s path(s).
Martin
On 2012-01-24 06:46, Julian Brooks wrote:
Hi all,
I'm looking for something that can quickly trim fairly long lists of
incoming OSC messages, for example:
slime/user/sb/app/renoise/midichannel/3/noteon/38 127
So that I can just get at '38 127'?
Theses lists are dynamic, so it's not possible to have them setup
beforehand apart from the 1st couple of strings.
I'm currently using a simple abstraction
[r $2]
|
[routeOSC $1]
|
[s $3]
that trims them down by copying and pasting (I also have a [print]
connected to the incoming messages) but it takes too long to get to the
data I want and it's hard to follow with so many messages flying past
the terminal.
This is for an improvisation system with several other people so there's
lots of data swooshing about, wondering if anyone has any experience
using OSC in this type of environment?
All tips, pointers, examples and patches gratefully accepted.
Very best wishes,
Julian
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
