Ok let’s consider that; by holding down the mod button, then wiggling two knobs, how would it distinguish between the two knobs wiggled being source & destination, versus two sources?
In addition, there are many mod slots, so in this way you would first have to enter the mod menu, choose the mod slot, then hold down the mod button while you wiggle two knobs to connect them, assuming that there is some interface method of letting the synth know that the knobs you wiggle are only source and then destination, and not the first two sources (unless you would want this operation to be only applicable to the first source).
Also, the previous value shown on the screen only applies to the saved patch, not whatever arbitrary value the knob was set to before it was wiggled, so if it was wiggled, and then you wanted to set it back to a very specific value, how would you do that easily without going through the process of listening carefully while you find the specific spot in the knob turn all over again?
Basically I think the knob wiggling to connect only would have to only apply to a very specific operation, like it would only connect the first source to a destination, and not choose two sources instead. Since you would still need to use the menu to choose the mod slot, and select the depth of modulation, and select a second source (which I do very very often) how is this dual-UX paradigm more elegant or intuitive than simply selecting the sources and the destination with a quick spin of the encoder? It takes no time at all to do, certainly less time than holding a button, wiggling two knobs, then taking the time to move them back to their original position (and then potentially going into the menu to select a second source with the encoder anyway if that’s desired). Very unconvinced by this. That’s not surprising though because I think the mod matrix operation is essentially perfect, it’s going to take a really good idea with a usage example to convince me.
You’re right that the Summit adds super useful controls for many things, it makes it way more fun to use versus the Peak and the dual filter is soooo good. I think a lot of the menu complaints of the Peak/Summit are due to infrequent use though, the menus are only a single layer deep and after frequent use I can jump into one and change the parameter I want almost instantly. I think people get one of these, do a lot of preset surfing, go to program a patch once in a while, try to find stuff in the menu, hunt for a bit, get frustrated, and post about how annoying it is to use. Just my guess, because I know from experience that it’s excellent and very quick. The old mod matrix though in the earlier firmwares? It was horrible for sure.
I want to @ calc (but I don’t want to bug him) to see what he thinks about some sort of touch connection for the matrix like you’re suggesting, maybe it has some merit if done right, like maybe when the mod button is held, the encoders that are moved won’t change their values internally at all, but just make the connection?
The other thing that leaves me unconvinced is that on the Summit, so many of the things you would use a mod matrix to connect are already hardwired as knobs and buttons to the front panel in a sensible way. Mod envelope 2 to pitch and LFO 2 to pitch both have a dedicated knob per oscillator, oscillator shape has a dedicated button to switch between modulation by Mod Env 1 or LFO 1 per oscillator, oscillator FM has a dedicated button to switch between modulation by Mod Env 2 or LFO 2 per oscillator as well as a dedicated knob per oscillator to control FM amount, the filter has a dedicated Osc 3 mod knob, a button to switch between Amp Env or Mod Env 1 and a dedicated to knob to select the depth of that modulation both positive and negative. So, yeah I use other modulations for sure, but a LOT of the most used bread and butter ones are on the panel ready to go.