Em ter., 24 de jan. de 2023 às 21:58, Christof Ressi <info@christofressi.com> escreveu:

7) Ideas for new objects:

* [split~] (or [moses~], etc.): take a multi-channel signal and split it into two different multi-channel signals at the specified channel offset.

it'd be nice to split more than just two, like MAX's [mc.separate~]
 

* [join~] (or [merge~], etc.): take several multi-channel signals and combine them as a single (multi-channel) signal. (Actually, the same functionality could be achieved by a more generalized version of [pack~] that also deals with multi-channel input signals.)


just for reference, that's MAX's [mc.combine~]
 

a) [sig~], i.e. [sig~ 0.1 0.5 0.7 0.8] would output a 4-channel signal.

+1 and it could take a list input as well to update values (like the [mc.list~] clone I was trying to code).
  

d) [expr~] and [fexpr~] :-)

of course :) 
 

---

Thanks for reading :-)


thank you
 

Christof

On 17.01.2023 04:23, Miller Puckette via Pd-dev wrote:
To Pd dev -

I've pushed what I think is working support for multichannel signals.  Many
objects haven't yet been adapted to deal with them, but there are enough to
at least test the concepts: lop~, send~, receive~, and (ugh) clone are
multichannel-aware, and new pack~ and unpack~ objects are provided to
combine and split signal channels.

I've put a couple of example patches on
http://msp.ucsd.edu/tmp/multichannel-tests.tgz
... the interplay between multichannel inlets and outlets and clone
are sometimes amusing.

cheers
Miller



_______________________________________________
Pd-dev mailing list
Pd-dev@lists.iem.at
https://lists.puredata.info/listinfo/pd-dev
_______________________________________________
Pd-dev mailing list
Pd-dev@lists.iem.at
https://lists.puredata.info/listinfo/pd-dev