Re: [PD] dynamically settable many-to-many cordless audio routing

2009-10-13 Thread Jamie Bullock
On 12 Oct 2009, at 21:41, Luke Iannini wrote: 2009/10/12 zmoel...@iem.at: Quoting Jamie Bullock ja...@postlude.co.uk: but then I can't easily script 'disconnect'. why not? Yo, I had a similar complete unawareness of the [disconnect( message long ago when I was designing a bunch of

Re: [PD] dynamically settable many-to-many cordless audio routing

2009-10-12 Thread Jamie Bullock
On 9 Oct 2009, at 16:03, IOhannes m zmölnig wrote: Jamie Bullock wrote: Hi all, Has anyone implemented this with externals, or a Pd dynamic patching hack? s~/r~ are one-to-many settable on the receive side. throw~/catch~ are many-to-one settable on the send side. What about a

Re: [PD] dynamically settable many-to-many cordless audio routing

2009-10-12 Thread zmoelnig
Quoting Jamie Bullock ja...@postlude.co.uk: but then I can't easily script 'disconnect'. why not? fgasdr IOhannes This message was sent using IMP, the Internet Messaging Program. binrPdr6GGmzM.bin Description: Öffentlicher

Re: [PD] dynamically settable many-to-many cordless audio routing

2009-10-12 Thread Luke Iannini
2009/10/12 zmoel...@iem.at: Quoting Jamie Bullock ja...@postlude.co.uk: but then I can't easily script 'disconnect'. why not? Yo, I had a similar complete unawareness of the [disconnect( message long ago when I was designing a bunch of dynamic audio routing stuff that caused me to architect

[PD] dynamically settable many-to-many cordless audio routing

2009-10-09 Thread Jamie Bullock
Hi all, Has anyone implemented this with externals, or a Pd dynamic patching hack? s~/r~ are one-to-many settable on the receive side. throw~/catch~ are many-to-one settable on the send side. What about a sendbus~/receivebus~ many-to-many settable on both sides? Jamie --

Re: [PD] dynamically settable many-to-many cordless audio routing

2009-10-09 Thread IOhannes m zmölnig
Jamie Bullock wrote: Hi all, Has anyone implemented this with externals, or a Pd dynamic patching hack? s~/r~ are one-to-many settable on the receive side. throw~/catch~ are many-to-one settable on the send side. What about a sendbus~/receivebus~ many-to-many settable on both sides?