Re: [PD] dynamic creation arguments for route
Dynaroute does something different than sroute-- you can send a list to its right inlet to change any or all of the creation arguments. You could also simply change the word "route" to "select" in the guts of the abstraction and have a "dynaselect," which might be handy for quickly setting key bindings. -Jonathan --- On Wed, 3/18/09, Frank Barknecht wrote: > From: Frank Barknecht > Subject: Re: [PD] dynamic creation arguments for route > To: pd-list@iem.at > Date: Wednesday, March 18, 2009, 9:27 AM > Hallo, > > also see [sroute] which is a hidden leftover in the > [list]-abs collection. > > The idea is to use a one-argument [select] instead of > [route]. [select] with no > or one argument has an additional inlet, where you can set > the thing it > selects. Decorate this with some [list split 1] and [list] > objects and you have > a simple settable [route]. No dynamic patching or externals > necessary. > > Ciao > -- > Frank > > Jonathan Wilkes hat gesagt: // Jonathan Wilkes wrote: > > > I built a settable route abstraction using dynamic > patching. It requires [initbang], which is missing in > pd-vanilla, so you'll need pd-ext if you want to use it. > > > > Let me know how it works if you try it. > > > > -Jonathan > > > > --- On Tue, 3/17/09, Ingo Scherzinger > wrote: > > > > > From: Ingo Scherzinger > > > Subject: Re: [PD] dynamic creation arguments for > route > > > To: pd-list@iem.at > > > Date: Tuesday, March 17, 2009, 5:25 PM > > > >Is is possible to dynamically alter the > creation > > > arguments for a route > > > > > > >object? > > > > > > > > > > > > [maxlib/nroute] can do that. The only difference > to [route] > > > is that it > > > doesn't eliminate the value that is routed. > This is > > > because it can be set to > > > any location of the list that's coming in. > > > > > > > > > > > > Ingo > > > > > > ___ > > > 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 > > > ___ > 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
Re: [PD] dynamic creation arguments for route
Hallo, also see [sroute] which is a hidden leftover in the [list]-abs collection. The idea is to use a one-argument [select] instead of [route]. [select] with no or one argument has an additional inlet, where you can set the thing it selects. Decorate this with some [list split 1] and [list] objects and you have a simple settable [route]. No dynamic patching or externals necessary. Ciao -- Frank Jonathan Wilkes hat gesagt: // Jonathan Wilkes wrote: > I built a settable route abstraction using dynamic patching. It requires > [initbang], which is missing in pd-vanilla, so you'll need pd-ext if you want > to use it. > > Let me know how it works if you try it. > > -Jonathan > > --- On Tue, 3/17/09, Ingo Scherzinger wrote: > > > From: Ingo Scherzinger > > Subject: Re: [PD] dynamic creation arguments for route > > To: pd-list@iem.at > > Date: Tuesday, March 17, 2009, 5:25 PM > > >Is is possible to dynamically alter the creation > > arguments for a route > > > > >object? > > > > > > > > [maxlib/nroute] can do that. The only difference to [route] > > is that it > > doesn't eliminate the value that is routed. This is > > because it can be set to > > any location of the list that's coming in. > > > > > > > > Ingo > > > > ___ > > 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 ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] dynamic creation arguments for route
I built a settable route abstraction using dynamic patching. It requires [initbang], which is missing in pd-vanilla, so you'll need pd-ext if you want to use it. Let me know how it works if you try it. -Jonathan --- On Tue, 3/17/09, Ingo Scherzinger wrote: > From: Ingo Scherzinger > Subject: Re: [PD] dynamic creation arguments for route > To: pd-list@iem.at > Date: Tuesday, March 17, 2009, 5:25 PM > >Is is possible to dynamically alter the creation > arguments for a route > > >object? > > > > [maxlib/nroute] can do that. The only difference to [route] > is that it > doesn't eliminate the value that is routed. This is > because it can be set to > any location of the list that's coming in. > > > > Ingo > > ___ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list dynaroute.pd Description: application/puredata dynaroute-help.pd Description: application/puredata ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] dynamic creation arguments for route
>Is is possible to dynamically alter the creation arguments for a route >object? [maxlib/nroute] can do that. The only difference to [route] is that it doesn't eliminate the value that is routed. This is because it can be set to any location of the list that's coming in. Ingo ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] dynamic creation arguments for route
Rory Walsh wrote: Is is possible to dynamically alter the creation arguments for a route object? no. (i general it is not possible to dynamically alter the creation arguments of any object :-)) I'm currently building a patch that receives OSC messages which I want to parse using route. Each relevant message I would like to grab starts with a unique integer ID. I would like to pass this unique ID to my route object each time the ID changes so that I can retrieve the data which follows it. Any ideas? you can build abstractions that behave almost like settable routes. you can also desing your application differently. mfgasdr IOhannes #N canvas 621 256 538 535 10; #X obj 48 57 inlet; #X obj 48 87 list split 1; #X obj 48 355 outlet; #X obj 48 229 t a; #X obj 161 57 inlet; #X obj 48 274 list trim; #X obj 48 254 list append; #X obj 230 350 outlet reject; #N canvas 0 0 450 300 demux 0; #X obj 108 53 inlet; #X obj 108 186 outlet; #X obj 247 207 outlet; #X obj 119 144 spigot 1; #X obj 245 140 spigot 0; #X obj 271 61 inlet; #X obj 271 83 t f f; #X obj 174 119 == 0; #X obj 295 105 != 0; #X obj 119 80 t a a; #X connect 0 0 9 0; #X connect 3 0 1 0; #X connect 4 0 2 0; #X connect 5 0 6 0; #X connect 6 0 7 0; #X connect 6 1 8 0; #X connect 7 0 3 1; #X connect 8 0 4 1; #X connect 9 0 3 0; #X connect 9 1 4 0; #X restore 48 303 pd demux; #X obj 49 206 t a b; #X obj 104 207 t a b; #X obj 148 252 t f; #X msg 86 231 0; #X msg 138 227 1; #X obj 101 161 f \$1; #X obj 48 184 select; #X obj 48 141 t a b; #X connect 0 0 1 0; #X connect 1 0 16 0; #X connect 1 1 6 1; #X connect 3 0 6 0; #X connect 4 0 14 1; #X connect 5 0 8 0; #X connect 6 0 5 0; #X connect 8 0 2 0; #X connect 8 1 7 0; #X connect 9 0 3 0; #X connect 9 1 12 0; #X connect 10 0 3 0; #X connect 10 1 13 0; #X connect 11 0 8 1; #X connect 12 0 11 0; #X connect 13 0 11 0; #X connect 14 0 15 1; #X connect 15 0 9 0; #X connect 15 1 10 0; #X connect 16 0 15 0; #X connect 16 1 14 0; #N canvas 621 256 538 535 10; #X obj 48 57 inlet; #X obj 48 87 list split 1; #X obj 48 184 select s; #X obj 48 115 symbol; #X obj 48 355 outlet; #X obj 48 141 t s b; #X obj 48 229 t a; #X obj 161 57 inlet; #X obj 101 161 symbol \$1; #X obj 48 274 list trim; #X obj 161 101 symbol; #X obj 48 254 list append; #X obj 230 350 outlet reject; #N canvas 0 0 450 300 demux 0; #X obj 108 53 inlet; #X obj 108 186 outlet; #X obj 247 207 outlet; #X obj 119 144 spigot 1; #X obj 245 140 spigot 0; #X obj 271 61 inlet; #X obj 271 83 t f f; #X obj 174 119 == 0; #X obj 295 105 != 0; #X obj 119 80 t a a; #X connect 0 0 9 0; #X connect 3 0 1 0; #X connect 4 0 2 0; #X connect 5 0 6 0; #X connect 6 0 7 0; #X connect 6 1 8 0; #X connect 7 0 3 1; #X connect 8 0 4 1; #X connect 9 0 3 0; #X connect 9 1 4 0; #X restore 48 303 pd demux; #X obj 49 206 t a b; #X obj 104 207 t a b; #X obj 148 252 t f; #X msg 86 231 0; #X msg 138 227 1; #X connect 0 0 1 0; #X connect 1 0 3 0; #X connect 1 1 11 1; #X connect 2 0 14 0; #X connect 2 1 15 0; #X connect 3 0 5 0; #X connect 5 0 2 0; #X connect 5 1 8 0; #X connect 6 0 11 0; #X connect 7 0 10 0; #X connect 8 0 2 1; #X connect 9 0 13 0; #X connect 10 0 8 1; #X connect 11 0 9 0; #X connect 13 0 4 0; #X connect 13 1 12 0; #X connect 14 0 6 0; #X connect 14 1 17 0; #X connect 15 0 6 0; #X connect 15 1 18 0; #X connect 16 0 13 1; #X connect 17 0 16 0; #X connect 18 0 16 0; smime.p7s Description: S/MIME Cryptographic Signature ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] dynamic creation arguments for route
Rory Walsh wrote: Is is possible to dynamically alter the creation arguments for a route object? I'm currently building a patch that receives OSC messages which I want to parse using route. Each relevant message I would like to grab starts with a unique integer ID. I would like to pass this unique ID to my route object each time the ID changes so that I can retrieve the data which follows it. Any ideas? [mrpeach/routeOSC] can do that. Martin ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
