jit.matrixset can't be named?

    May 03 2006 | 12:37 pm
    I'm sharing a jit.matrixset amongst different locations in my patch.
    Normally with a jit.matrix, you give it a name and you're done. Names don't
    seem to work with jit.matixset. I need to query an outputmatrix at location
    A while not sending it to B or the other placed I use the matrixset. I can
    think of a workaround by using a jit.matrix @thru 0 at the
    jit.matrixsetoutput, but am I overlooking something? Is there a reason
    for the object NOT
    to have a name attribute?

    • May 03 2006 | 1:07 pm
      hoi thijs,
      as far as i know (which might not be far enough ;-) there is no way
      to reference the matrices of a jit.matrixset by names.
      have a look at mxj matrixlist, which makes this and other nice things
      jan klug
    • May 03 2006 | 1:59 pm
      Hi Jan, thanks for the tip. I wanted a global reference to the matrixset
      object global, just like jit.matrix can. I'll have a look at the java thing
      and figure something out.
      best, thijs
    • May 03 2006 | 5:39 pm
      a good workaround is to put it into an abstraction with a set of named
      send and receive pairs and voila - a named jitter matrix buffer!
      save this as matrix-buffer.mxb and load it into any patch. you can
      easily expand on this idea to write into the matrix.
      all the best,
      max v2;
    • May 04 2006 | 3:44 pm
      Hey Thijs,
      My new favorite solution to this is to use the poly~ object to create a
      bank of named jit.matrix objects. The named matrices can then be called
      whenever you need them by naming your output matrix. The sprintf object
      is your buddy. See attached patch. Coming soon to a Recipe book near you.
      Andrew B.
    • May 04 2006 | 4:15 pm
      Thanks for the replies. For my patch, it was vital to read and write the
      matrixset to files as quickly an easy as possible. I really like that about
      matrixset. I solved my problem by simply putting a (temporary) matrix at the
      output. Request the matrix I need, dump the output to anywhere I need it,
      request another, etc. works like a charm.