Dunno if this would be of any use (attached) but I've been making use of [entry] to keep an eye on incoming OSC streams so instead of hundreds of messages whizzing by this allows to just see when the data changes. Shouldn't be too difficult to parse and dump the various OSC addresses either.

Thanks to Mike MB for helping figure the dataflow.

Cheers,

Julian

On 7 August 2013 14:55, Dan Wilcox danomatika@gmail.com wrote:

Ah, that's much simpler than what I was thinking. How do you always do it Roman? :D

On Aug 7, 2013, at 9:44 AM, pd-list-request@iem.at wrote:

*From: *Roman Haefeli reduzent@gmail.com *Subject: **Re: [PD] routeOSC - dynamic routing?* *Date: *August 7, 2013 7:16:13 AM EDT *To: *pd-list@iem.at

On Wed, 2013-08-07 at 02:15 -0400, puredata@11h11.com wrote:

hi all,

i have more than 50 OSC messages to [routeOSC], i would like to avoid having to cut and paste & click and drag. what are my options here?

[routeOSC /knob1 /knob2 ...] | | [s $0-knob1] [s $0-knob2]

thanks

Instead of routing with [routeOSC], you could use the last address field directly as the send address:

[/knobs/knob1 23( | [routeOSC /knobs/ | [list] | [; $1 $2(

As an alternative to the ;-messagebox with hard-coded number of elements, you could employ a settable [send]

Roman

---

Dan Wilcox @danomatika danomatika.com robotcowboy.com

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list