Clever, but you have to do a repetitive error-prone lengthy clicky process either on the send side or on the receive side.
Since in my case i have four 16-tracks sends to a 64 by 16 matrix (3rd order ambisonics monitoring), i mitigated the issue by making an abstraction containing 16 settable sends, taking a float as an argument for the first send number. On the other side, i still had to make 64 unique receives...

Le ven. 5 juin 2020 à 20:23, Dan Wilcox <danomatika@gmail.com> a écrit :
Your abstraction can have a named [send~] which you can receive into your matrix. Use the $1 id assigned by clone to differentiate the sends, ie.

In abstraction:

|
[send~ out$1]

For matrix:

[receive~ out1]  [receive~ out2] [receive~ out3]
|                |               |
[matrix          -               -          ...]

etc

In this way, the [clone] itself has no outputs, but you have all of the outputs via [send~]. I use this approach very often.

On Jun 5, 2020, at 7:49 PM, pd-list-request@lists.iem.at wrote:

Message: 5
Date: Fri, 5 Jun 2020 19:20:36 +0200
From: baptiste chatel <baptiste.chatel@gmail.com>
To: Pd-List <pd-list@lists.iem.at>
Subject: [PD] [clone] with individual signal inlets/outlets exposed ?
Message-ID:
<CABrNpLyvGHrRV-+9wDj2p8NnZENQDwEgg-tO7yFHEjw5L1eV6Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Would it be possible to have a [clone] option that allows clones individual
signal inlets/outlets to be exposed ?

An example : i need to make 64 of the following patch :
[receive~ thing-$1]
|
[outlet~]
that should go to a matrix, $1 in [1:64].

[clone] is useless because it will sum all outputs and expose only one,
since the cloned patch has one output.

I could do it with dynamic patching, but as practical as it could be, it is
pretty convoluted to use for such a simple need.


Baptiste

--------
Dan Wilcox