I'd like to join a large number of oscillator outputs into a single bus with [join] and then disaggregate them at the other end. Is there an object that sends each item in an intput list to a separate output?
-
Inverse of [join]?
Game and graphic designer, sci fi illustrator & author, teacher, sound hacker, plus some other shit.
-
@JoshuaACNewman Depends on exactly what the data is that you are joining, you say it is the output of a large number of oscillators but those are audio rate and the only [join] I know of is message rate. Are you sampling the output of the oscillators with [snapshot~] or the like? Than [unpack] can do the just since those outputs would just be floats? But then why use [join] instead of [pack]? Why are you joining them just to take them back apart again? If you are talking about [cyclone/join] than there is no direct inverse, if the first inlet to [join] is getting a list of floats and the other inlets getting single floats there is no way for pd to know where the list of floats ends and the single floats begin since [join] outputs a plain old list. So it is up to the user to undo such things. I think you will need to supply some more information to get useful responses, but someone else may have a better idea as to what you are getting at,
-
Thank you.
The only reason is that I'm trying to avoid a tangle of wires in order to keep my head straight! I saw it worked at message rate and was wondering if I was missing something.
Game and graphic designer, sci fi illustrator & author, teacher, sound hacker, plus some other shit.
-
@JoshuaACNewman I generally use subpatches, and combine those objects and all their wires into one subpatch, but {send~] and [receive~] are the standards, [catch~| and [throw] can work in some situations but their message rate control can be troublesome.