[PD-dev] help designing multichannel aware externals

[IOhannes m zmoelnig]

On 1/25/23 17:09, Miller Puckette via Pd-dev wrote:
> I think I hadn't pushed them, oops.  And now I'm thinking again - maybe it's
> more elegant yet to provide empty output signals (channels=length=vec=0)

conceptually, i like this; though i would suggest "channels=0; 
length=64" (or whatever).

> and instead of (for example)
>     sp[2] = signal_swapforchans(sp[2], outchans);
> you'd just write
>     signal_setchans(sp[2], ouchans).

hmm, wouldn't that modify the t_signal* struct that sp[2] points to, 
potentially breaking the reuse? (so it ought to be 
"signal_setchans(&sp[2], outchans)")

and i find the "swapforchans" slightly confusing (which fo(u)r channels 
are being swapped? the actual swapping is done by re-assigning a new 
value to sp[2]).
so how about:
   sp[2] = signal_makemultichannels(sp[2], outchans);


gfmasdr
IOhannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20230125/da97960e/attachment.sig>