New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missing/useful [snake~] methods #1996
Comments
what's the advantage of |
being able to create multichannel signals with a different number of channels according to the list input length |
I think these are all useful, but I would prefer different names:
Two more methods:
|
since split feels like the verb from list split, merge could be [snake~ append] and [snake~ prepend] ? |
Prepend/append only makes sense for control objects where you have hot and cold inlets. For signal objects you only need a single method. |
oh, understand, i thought about avoiding crossed connections, but it is silly xD and what about an object to take specific channels from a signal? not sure about the verb... get/take/reorder... ? [snake~ get 1 3 2 4] could take an arbitrary signal with n channels and swap 3 and 2 channels and return just a 4 channel signal from the n channel input, would this be possible with the current objects? maybe this could even be used for a specific duplication of signals [snake~ get 1 2 1 3] could take a 3 channel, and output a 4 channel with the third signal being a copy from the first signal from the input if the number of channels is lesser than the number expected, so just insert an empty signal there and we could also drop some channels like [snake~ get 4 2 6 3] ignoring 1 and 5 and reordering everything what do you think? |
+1
I really like the |
I miss "Magic Glass" more than anything else from Pd Extended. An enhanced version capable of showing multichannel values (and control values) would be useful. |
@whale-av while all of your suggestions are related to multichannel, none of them is related to |
I apologize... I clicked the wrong thread link after registering to post. |
an issue to discuss and propose more [snake~] methods
The text was updated successfully, but these errors were encountered: