Controlling a large non-binary matrix~
I’m currently building a large modular patch with about twenty modules. Routing is through a 20×20 matrix~ running in non-binary mode. I really like this mode as it allows for subtle feedback between modules, but I’m having trouble building an efficient UI for it, or rather one which doesn’t take up the whole screen. At the moment I’ve got a 20×20 grid of Live dials.
Anyone else thought of a better solution?
Matrixctrl in dialmode? You’d just need to provide or create dial graphics…
Thanks, I didn’t know matrixctrl had this feature. Just the ticket.
Roger, thanks for sharing. I think the dialsml.jpg is about right for me, but I’ve been playing with it for a while and can’t quite work out the settings?
This using FrameDialSml. For a reason I didn’t work out yet,(probably the number of rows in the image) DialSml doesn’t seem to work properly) Assuming the files Roger supplied are located in one of your Max search paths…
-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 459.3ociS0zabBCD8L7qvxmoHv.KndqQQ4VO0iQUQdgIrdiwFY6MYahx+85O .h2nMR4hg4MOddl2L7VZBdu7LnwnehtGkj7VZRhGxAjrDmfmnm64TsmFdBzZ 5HfyB4LvYiGu.UfJIqvyTS+AlX7AEzaBxSZqxapaq1UkgHjt7tcUMjlLT8t7 hLTo8D82kuVbZhI3fweijEvGkBil8J3vJKreyFW4IyJ4xEz.j4eyP3xw3MwY C95Ut+3OpvQZKnSdx3eoXTN1k38zT2Q120ZnFE6buQwW0cvpjQQ6exZEw8xU rmphhM6otIustkPruV11Erm5H+QIeweicWyuVsfdfymYA4w2orc2s1p4OS77 iyieLmbILf5APP2y8Fv0c10R+YPYX8T9DUMxDw7UTwXX5T8USANSavYKO2Zm YEnAggZXRQji3lwgCRg2Dp65hLgn4HI1umjCPrOr+oQwvlQ7a+L5V3Q5It4F Wp7YapEtGjJ1q1cgKZunMA+kaqdwm+mwOPc3WtdnkmT8qM+Rkh9nEF.sgI78 cDG6VIpbiyA1v.bgOOvztQ0v0KN57rcDoWjzWH1EyiRkKbWlOjIBgdEwJ3Y1 J+lTmZum9ePuJv+B -----------end_max5_patcher-----------
And while I’m at it, here is one of my home brewed varieties, IMO a tad easier to get a visual cue on states and matrix "overview" than pointer type dials provide. Also has a slightly greater number of steps (0-20). JPG should be attached…
Edit: appears the forum software has removed the hyphen (after "sa") from the jpg filename , so that will play havoc with the attached example.
----------begin_max5_patcher---------- 571.3ociT0ziZCCD8bxuBKeNDvNjPXu0pUp8BRqTUOUUgLICACI1Q1FV5tZ+ uWamDHrEj5Eim2Ld93Muv6gA3MxyfFidB8KTPv6gAAdHGPPuc.tgctnlo8gg a.slUA3nNeF3rwiOCMCQRGfaYlhcbQ0ZETX5ROMiFOKBMeAIdFklSWXum4PH 1Szu6en3XCWTCFewn8fakBil+F3vHyru4RrxilgfI8ncPl+zBc0Eiuj7VEnA ggY3Rw3NKMKljQRyhPoKximOmRiPtx3Nt7XdoeNka1OYNdTiIXM9Jg+hhypw NGeDF5Nh9eoTlQwOWXT0C48DScIs+q2RacLJVwAKAOlltGomuzMGIyW3YZBI Nc4xbZR28jj7E4IWlPk70Nljbukw.XATW2x6J.dEqfKLR8t0e+4ml9SMnzS0 F3DHXkrloqXmW8iWV+pTcX52.A5ENT.tavItMHTqyFoMG2tcJXJkUhI1Uj7n p.r4gMoa1OHjazj38sUWkWJK8X.0Zag1T6Ip6qJF3lSfxvKX0MLUEWLN9BY8 wFQ2HlLvDLQkOozGppp4ZCNp+2qhDwItla6nMGpDkiosGn8Ho9Ei+jl4EcT5 Cjc4iE.MxRXb98EbzdwQbOCaYGqMe04Jt05pO1cRE+Mqz8F5Xjv0Wb6jI97e M3UXN7aUycardhouSQWGgRPa3B+jOJF6GQHxkX1wKKga1Kkbsa0Vd+li01ZW o59T5aD6WJ6kJmYVj2jK5L8YDq.2poK9zPW19H7ut6hPq. -----------end_max5_patcher-----------
Thanks Spectro, that’s just the ticket. I really appreciate the effort.
I think my problem was that I didn’t realise putting in a background image was necessary. But those are both working fine.
spectro, that is awesome. well done.
Sounds like you’ve got it working, and I’ve found that matrix~ is generally fairly efficient. As an alternative approach, you can use poly~ with send~, *~ and line~) and receive~ and dynamically change the targets of the send~/receive~ objects. This is good for situations where you want to be able to make connections, but you’re not making 200 of them at once, or where you need more flexibility in adding modules. Just one for the bag o’ tricks…
Also, you may find this helpful for mixing:
It turns a matrix~ into a giant mixer complete with mute, solo, etc. all controlled by lists.
last week or so, I was using max 5 and had spectro’s dialmode graphic working fabulously. Now I’m using max 6 and the image isn’t working at all, and looks totally different. Anybody know how to fix it?
I think I’ve figured out what was wrong — it was a matter of choosing the correct cell range in the matrixctl attributes — in this case, 21.
Forums > MaxMSP