This may be a bit off-topic, but here it goes anyhow. If you guys need dynamically setable receives that will not crash pd, try the latest pd-l2ork (version 20120607).
Cheers!
Ivica Ico Bukvic, D.M.A Composition, Music Technology Director, DISIS Interactive Sound & Intermedia Studio Director, L2Ork Linux Laptop Orchestra Assistant Director, CCTAD Virginia Tech Department of Music Blacksburg, VA 24061-0240 (540) 231-6139 (540) 231-5034 (fax) disis.music.vt.edu l2ork.music.vt.edu ico.bukvic.net
Cyrille Henry ch@chnry.net wrote:
Le 08/06/2012 19:15, Jonathan Wilkes a écrit :
anyway, if you really in need for a settable send and a settable receive, you can always use prepends and route that are both settable. see small attached abstraction.
I think you are stuck for two reasons
- [r setable_send_receive] is global. I want the parent $0 in front of it so that
my abstraction symbols don't clash with other abstractions.
i don't understand this point : just ignore the settable_send_receive stuff that is hidden inside ss and sr. this 2 abstractions work exactly like a real settable send and receive, at least for the local / global send. i.e. if you want a local only send/receive, just use $0-bla, like you would have done with "real" send / receive.
that the route that filter content of different abstraction. the only problem is CPU overload, but that should really be minor.
- Your example filters messages in a way that s/r doesn't. It's possible to hack
around this using three extra objects.
yes, right. but that is a minor problem. not a show stopper.
cheers c
It is also possible to get the arguments of an abstraction in Pd Vanilla. With the former, I'd rather send a single message to an inlet and be done.
-Jonathan
cheers c
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list