I'm a beginner currently working on a 24/24 Toggle matrix to use as a general purpose tool for patching.
The Toggles are organized in a square grid inspired by a design used by a few vintage synths to connect modules together. The toggles basically function as ON/OFF switches for patching signals in a synthesizer.

For example, if the output of a sine wave oscillator is sent to horizontal row ( 4 ) and the input of a filter is connected to vertical row ( e ) they can be connected together by triggering the toggle e4.

By sending (send) or (receive) messages in a message box I was able to give several toggles the same row name. I started manually numbering these but then realized that I’d have to name 1152 of them! Half of them sending and the other half receiving with different letter and number combinations.

Is there a way to give the toggles a two part message that includes the numerical row and the alphabetical row so I don’t have to manually add a number?
Or do some kind of row check similar to a button matrix?

Patch Matrix 1.pd

@high_output-5000 no. a couple times in the past I've used awk for stuff like this (use awk on the .pd file)

you could try wrapping the row in an abstraction, then give the abstraction an argument to set the row number. Then you would just have to set each column number..

another solution might be to create a one-time dynamic patching section, and just use it to generate the matrix. you can set the send and receive names before you create the objects, then create them with the 'obj' canvas message to the canvas

I've used [matrix~] from iemmatrix with [numberbox_matrix] from iemgui to do this kind of stuff. Because then you can also set an 'amount' for each signal

edit: for example this polysynth: https://github.com/sebshader/instr/tree/master/datalogue
(tho the editor is separate from the synth/signal matrix & the synth guts are pretty ugly)

@high_output-5000 I think I've done stuff like this using nested [clone]s, e.g. the inner clones each represent a row for a particular column, and the outer clones represent the columns. The outer clones pass their column identifier to the inner clones. I'm just handwaving due to cocktail hour...let me know if you need more detail and I'll get on it!

@jameslo That sounds interesting! How do you set up the clone architecture?

@high_output-5000 I generally use dynamic patching for such things. Here is one for a 10x10 grid which I yanked from on of my patches, gives unique send and receive symbol to each. Just hit the bang and open the subpatch to see your toggles. No time to go into detail but you should be able to figure it out and how to tweak to your needs without much effort.
togglepatch.pd

@high_output-5000 said:

@jameslo That sounds interesting! How do you set up the clone architecture?

Maybe like this? https://forum.pdpatchrepo.info/topic/13500/signalrate-matrix-mixer Let me know if this is not right (and please explain how it's not right) and I'll see if there's a way to make it meet your needs if you can't see it before me. Definitely check out @oid's suggestion too.

@jameslo @seb-harmonik-ar

Thanks! The toggle patch works like a charm!! This will save years of my life!

I'll just make a copy and send a message to the toggle objects to clear the receive of one and the send of the other.

@high_output-5000 I think [matrix~] is the way to go as @alexandros suggests..... as it avoids building a matrix of [*~] controlled by the toggle matrix.
I have dynamically patched audio connections directly in the past... but of course clicks as connections are made and broken.
I had missed [numberbox_matrix] and would definitely have used that to create the messages to [matrix~] if I had found it at the time.
It is a very simple solution with no need for sends and receives. You can pass the messages directly from [numberbox_matrix] to [matrix~] and set the fade time in [matrix~] to avoid clicks.
But it means putting a number 1 or 0 in the numberbox rather than just clicking a toggle....... so building a toggle matrix might be better...... however.....

If you only needed one toggle selected at any time then [grid] is back on Deken thanks to Lucarda..... and if you set x max and y max to the same as the number of squares in the [grid] it will output the data you need to control [matrix~].
So for my twopence...... [grid] and [matrix~] gives instant relief for a single toggle selection.

Last thoughts.......
A Data structure could well be easier to build than a toggle matrix and easier on the cpu @jona.
If you are sending any to any (any input to any filter) you could use radio buttons instead of toggles.
Or Ofelia could do the job........ https://forum.pdpatchrepo.info/topic/11792/ofelia-test-grid .... but is a bit heavy.
David.

@whale-av have I suggested something in this thread?

@alexandros He he he....I think David meant @seb-harmonik.ar. At least you were associated with a good idea

@alexandros Sorry @alexandros...... but you are always worth a mention......
David.