Is there already some non-binary matrixmixer~ with signalrate modulation inputs?
How would you patch such?
A smart way with [clone] and subpatches?
Ideally I'd like to create
[mmix~ 4 4]
and get 4 inputs~
4 outputs~
and 16 modulation-inputs~
signalrate matrix-mixer~ ?
Is there already some non-binary matrixmixer~ with signalrate modulation inputs?
How would you patch such?
A smart way with [clone] and subpatches?
Ideally I'd like to create
[mmix~ 4 4]
and get 4 inputs~
4 outputs~
and 16 modulation-inputs~
@lacuna I dunno, maybe this?
matrixMixerMaybe.zip
Look at the toggle sends to see the modulation input names. There are signal rate receives on the other end, but I just used toggles to test. The whole thing probably accrues 2 blocks of latency along the way, but I didn't test.
Edit: I don't understand why, but I'm not getting any delays. Did I create the objects in some magical order?
Edit2: What's the matter with me? The modulation receives are control-rate. But you can easily change them to audio-rate and ditch the toggle matrix I used to test.
Oh, I didn't know it was possible to specify the number of clones from an argument! This is even closer to @lacuna's request:
matrixMixerMaybe2.zip
for 4x4 i would not bother.
for 16x16 you might, depending on the use case, choose to make individual dsp circuits which only turn on when required for rows, columns, or 4 pieces of 8x8.
@lacuna This was a nice excuse to finally look into dynamic patching, thanks. I built something to create all the s~ and catch~ objects for me. It assumes that the modulation inputs are signal rate as you originally requested.
generate matrix mixer.pd

@jameslo marvellous, thank you very much!!!!
Just added inlets~ and outlets~

EDIT:
Guess what, I couldn't hear anything )
Bug fixed: [r~] instead of [r]
mm_send.pd
Oops! Looks like something went wrong!