I wish i was as skilled as you think i am ! I'm the one impressed by your work with Cyclone and Else while describing yourself as not so skilled in the externals programming domain :)
To add to the noise : your -mcin -mcout option idea is great ! Sure, there are many ways to do without this in my case, but the general idea is to improve on [clone] to be able to do quickly and simply things instead of engineering convoluted workarounds (not trying to say that the work involved by such an upgrade to [clone] is easy).
Actually, i would be very satisfied by :
and lonely because i have to rename 64 [receive]s.
Le ven. 5 juin 2020 à 21:10, Alexandre Torres Porres porres@gmail.com a écrit :
I guess making noise on the list helps :) it narrows down to someone also feel it's worth it and implement it, aren't you a skilled fellow anyway? I think this one is over my head... I'm still only able to managing lower hanging fruits :P
Em sex., 5 de jun. de 2020 às 15:30, baptiste chatel < baptiste.chatel@gmail.com> escreveu:
Is there a way to nicely "upvote" this request other than commenting the issue ?
Le ven. 5 juin 2020 à 20:16, Alexandre Torres Porres porres@gmail.com a écrit :
I already made that request by the way https://github.com/pure-data/pure-data/issues/500
Em sex., 5 de jun. de 2020 às 14:51, baptiste chatel < baptiste.chatel@gmail.com> escreveu:
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
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list