> naming of [pack~]/[unpack~]
Maybe they also could be called:
[group~]/[ungroup~] ?
___
Pd-dev mailing list
Pd-dev@lists.iem.at
https://lists.puredata.info/listinfo/pd-dev
OK... now I'm hesitating between "snake~ in", "snake~ out" and "snake~ tap"
or "join~", "split~", and "tap~"...
Former is more colorful (and crowds the namespace less). Latter might be
easier for non-native English speakers to deal with?
cheers
Miller
On Wed, Jan 25, 2023 at 01:36:24AM +0100,
OK, just now changed this - there's a one-channel signal created for all
signal outputs. Now if you want more than one channel you have to call
signal_swapforchans() (see d_arithmentic for example).
cheers
M
On Tue, Jan 24, 2023 at 08:07:22AM +0100, IOhannes m zmoelnig wrote:
> On 1/24/23
Em ter., 24 de jan. de 2023 às 21:58, Christof Ressi
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
> I find [snake~] and [unsnake~] quite funny :-)
I'm glad I'm not the only one :) and usually Pd has some funny names, so it
felt quite proper to me ;)
Em ter., 24 de jan. de 2023 às 21:58, Christof Ressi
escreveu:
> Hi all,
>
> I am a bit late to the party. I finally got around studying the
Hi all,
I am a bit late to the party. I finally got around studying the new
multichannel code changes and wading through this massive sea of e-mails
to get up to date on the discussion :-)
First off, I am very excited about this new feature! Here are a few
comments from my side. The e-mail
Isn't "mux~/demux~" closest to what's actually happening?
Unfortunately, these are also zexy objects ;-)
On 24.01.2023 11:52, Max wrote:
Isn't "mux~/demux~" closest to what's actually happening?
when "joining" two signals, I wouldn't expect them to be running in
parallel but being mixed
Isn't "mux~/demux~" closest to what's actually happening?
when "joining" two signals, I wouldn't expect them to be running in
parallel but being mixed together.
m.
On 24.01.23 02:50, Miller Puckette via Pd-dev wrote:
So merging (hmm) some ideas from Fede and Dan, maybe "join~/split~", and
a
About the debugging suggestion, what about enhancing [nop~] to became graph
on parent with one number box showing the number of channels?
this way we can select a connection and do Ctrl + t (triggerize) and get a
[nop~] showing a number box inside
it of course needs to show its name, so we can
sorry for double posting, but for my idea to work i think [inlet~] should
receive an outlet that gives the number of channels, this makes trivial to
then update [nop~] to give the functionality i mentioned
Em ter., 24 de jan. de 2023 07:20, José de Abreu
escreveu:
> About the debugging
I think the proposal join~/split~ is the one I prefer.
It follows quite well the naming of other pairs like throw~/catch~ or
send~/receive~.
Just a personal feeling...
Antoine
Le mar. 24 janv. 2023 à 08:25, Matt Barber a écrit :
> I was also going to suggest snake~ as the accepted hardware
11 matches
Mail list logo
