Hey all,
So, what is the functional use of snake~?

I can get the object to work if there is a direct connection to a snake~ out.

However, I tried to use a send~ to a receive~ object with a name like test_snake, and the receive outlet only recognizes the first variable.

Am I doing something wrong? I could see the use of this object if I could send the data to another object, but cannot think of the right object to use to send all of the channels of data.

@raynovich "Snake" might derive from the old familiar name for a "multicore" audio cable.
[snake~ in] is like the stagebox and can have many inputs, and [snake~ out] is like the "fan-out" end of a multicore at the mixing desk.
But the interesting use is that an audio object like [+~] or [pow~] is also multichannel, and can be inserted in the multicore.

For [send~] and [receive~] you must specify how many channels for [send~ name x] and then [receive~ name] will automatically have the same number of channels..

There is now a sub-patch for audio object help....... [pd multichannel] and if you open that from within the [send~] help file you will see how it works.

I don't understand why [send~] needs the channel count specified while other audio objects just "know"... that seems strange.

There are still bugs in multichannel though.
David.

thanks. Got it and it works and your help is much appreciated.

I don't understand why [send~] needs the channel count specified while other audio objects just "know"... that seems strange.

The reason is that a matching [receive~] might be scheduled before the [send~]. At this point, the [send~]'s "dsp" method wouldn't have been called yet, but [receive~] already needs to know the channel count. Note that you can still change the channel count dynamically with the "channels" message.

As a side note: with [throw~] and [catch~] the relationship is reversed: [throw~] does not require a channel count, but [catch~] does.

There are still bugs in multichannel though.

What about reporting them?