Hi Mario,
On Mon, Sep 23, 2013 at 08:44:15PM -0300, Mario Mey wrote:
Your router.pd is the one I was looking for for the router
connection. Because I had done a dozens-of-wires connection... a
mess. I use that technics, now, it is beautifull. Thank you.
Great to hear!
Is it better to have
On Sun, Sep 22, 2013 at 12:09:53AM +0100, Ed Kelly wrote:
if you can I would prefer to patch with direct connections as it may make
things clearer. Attach is a little sketch (router.pd) which uses no
signal-sends and -receives at all, so you can be sure to have no delays
introduced. Still
Hi Mario,
if you can I would prefer to patch with direct connections as it may make
things clearer. Attach is a little sketch (router.pd) which uses no
signal-sends and -receives at all, so you can be sure to have no delays
introduced. Still you can route all over - but of course feedback paths
On Thu, Sep 19, 2013 at 01:52:37PM -0300, Mario Mey wrote:
I was guessing... if I made a sum of delays using so many send~ /
receive~ and throw~ / catch~...
For a full use of my patch (mic input - FX-A - FX-B - output), I
have this structure (inside subpatches and abstracts):
...
Does
I think most of s/r and throw/catch are between abstracts. If I want to
sort that objects (as Theory of Operation says: creating receive~ after
send~)... I don't know how to do it.
Does the sorting include creation of abstracts? I mean, should I
cut-paste from the objects (s/r, throw/catch
Hi,
On Thu, Sep 19, 2013 at 02:20:28PM -0300, Mario Mey wrote:
I think most of s/r and throw/catch are between abstracts. If I want
to sort that objects (as Theory of Operation says: creating receive~
after send~)... I don't know how to do it.
To trick Pd into sorting signal objects, that are
