FYI, if you want a snake out of tabread4~ but are assigning the source arrays dynamically, do yourself a favor and at least provide dummy table arguments in your declaration. If you don't, tabread4~'s output will always be a single channel, no matter how many tables you try to set afterward.

There! If you are as slow as I am, I just saved you 2 days of head scratching. I would not be surprised if this was also true for tabread~ and tabplay~ but I didn't test. Oh, and I'm running Pd 0.55, although I started this patch a version ago where I probably had the same issue but couldn't hear it due to other even worse issues

thanks for the note! - as a little gesture of solidarity, i spent many hours this weekend trying to fix an issue in an external until i found that i had a typo in the message i was sending to it in my patch.

about this one here: i was surprised first, since it would certainly feel intuitive to dynamically change the channel count that way. at least for [send~], it can be set dynamically. not sure why this is not possible here. maybe it would require a dsp reset? that's just a random guess though ...

@ben.wes said:

i was surprised first, since it would certainly feel intuitive to dynamically change the channel count that way.

I get the feeling that changing a channel count dynamically is something that's obvious to humans but harder to implement than one might have thought. In SC, you can change a channel count by stopping the synth node in question and starting a new one with the new topology -- and there's no other way. Multichannel send/receive has at least one restriction that's noted in the help file (changing receive size requires switching DSP off and on again).

One possible tricky point is that an upstream change of channel count would have to cascade through downstream objects.

Anyway I don't know Pd implementation details so I haven't got much to add to what I just said.

hjh

Objects in ELSE cam resize without a problem as they force a DSP update, so can [adc~]... not sure why it's avoiding it in other vanilla objects, I hope it's not laziness, but it's simple and trivial to do, just force a dsp update (which turning off and on dsp also does)