Matrix Solo Mute


    May 03 2006 | 11:36 am
    I have made a matrix~ which is controlling the output of my signals. I have a mute system working in which I have toggles connected to (== 0) and message "0 0 $1" "1 0 $1" etc. The "== 0" is in order to get the channel closed when the toggle is on. The problem I am having is with my solo system. I have solo messages hooked up to the matrix~ which sends the values for just one channel to be open, for instance "0 0 1 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0" for just channel 1. This works but I want to be able to restore channels which were muted before the solo.
    I tried storing the matrix~ values before the solo and then have them retriggered/sent to the matrix when the solo toggle is released but that proved non succesful.
    I have read a number of threads regarding similar topics, and alot seem to be having the same problem but none relating to restoring previous matrix~ info.
    Is there a way to do achieve what I am trying in restoring this info to the matrix~ ?

    • May 03 2006 | 11:58 am
      Here is a section of the patch. I have got it to store the values from the matrix~, using "getrow 0", in a coll under store location 2. This is in order to recall it to the matrix~. I cant think of a way to exclude the solo values from the coll though unless I were to put a bunch of if statements basically saying if input = 0 0 0 0 1 0 0 then 1, and have it store to coll location 1.
      max v2;
    • May 03 2006 | 5:04 pm
      I posted a solution for this a couple of months ago, using vexpr and
      one of my matrix~ helper objects. (IIRC it was PM.MatrixSetOutlet) If
      you remove the inlet/outlet info and treat it as a list of gain
      coefficients, the math is easy, and then it's just a matter of
      reintroducing the coordinates. (I use multisliders both for the faders
      and for the solo and/or mute buttons (int 0-1))
      Peter McCulloch
    • May 04 2006 | 10:17 am
      The canada ad looks like a bit of spamming.
      I managed to fix something up using a gate and the matrix, basically changing the gate when I want it to hold the solo info and the other gate for mute to restore to.
      It may not be the most efficient method but it works for me. Only thing is I am having trouble with the asthetics of the solo and mute buttons, as I want them to correspond to whats going on in the matrix as in all mutes off when a solo is on and then mutes restored when the solo is off.
      I am sure you can all see the problem of Max creating loops if I just tell the buttons to related to the matrix info. I have made the toggles for both buttons but am thinking maybe I would be able to get round this problem quicker using invisible buttons on top...?
      Will
      max v2;