autopattr bug ?


    Jun 11 2007 | 10:42 am

    • Jun 11 2007 | 11:05 am
      On 11 juin 07, at 12:42, guillaume wrote:
      > i'm facing a problem (bug?) with autopattr and ctrlmatrix, it seems
      > autopattr doesn't like large matrix.
      > i'm using max 4.6.3.
      The problem is that the number of items to store is astronomical. 102
      (col)*81(row)*3(x,y,state): 24786, AFAIK, autopattr have the same
      limitation as the list length (4095). I would suggest other strategy
      involving storing only the on points (dump the row/col, store the non
      0 states).
      Best,
      ej
    • Jun 12 2007 | 9:24 am
      guillaume schrieb:
      > i'm facing a problem (bug?) with autopattr and ctrlmatrix, it seems
      > autopattr doesn't like large matrix. i'm using max 4.6.3.
      >
      > thanks for your help
      Beside the explanation of Emmanuel, you might rethink your UI design. A
      matrix of this size is more like a picture, maybe you can better achieve
      what you want to do with jitter or LCD... You'd need to store it
      differently than with autopattr though...
      Even with a matrix of that size it should be possible to dump it into a
      coll, and save the coll with the patcher...
      just some thoughts...
      Stefan
      --
      Stefan Tiedje------------x-------
      --_____-----------|--------------
      --(_|_ ----|-----|-----()-------
      -- _|_)----|-----()--------------
      ----------()--------www.ccmix.com
    • Jun 12 2007 | 10:13 am
      i explored a little the coll solution, but this doesn't seem to be really easy... in fact my 54x54 matrix is a router controller, i managed to do it another way, with a lot of ubumenu. it's more user friendly, you know a little bit better where each sensor is sending data.
      G
    • Jun 12 2007 | 10:33 am
      On 12 juin 07, at 12:13, guillaume wrote:
      > i explored a little the coll solution, but this doesn't seem to be
      > really easy... in fact my 54x54 matrix is a router controller, i
      > managed to do it another way, with a lot of ubumenu. it's more user
      > friendly, you know a little bit better where each sensor is sending
      > data.
      This is what I usually do. It can be optimised but this is just the
      idea.
      ej
    • Jun 12 2007 | 12:30 pm
      thanks emmanuel
      i thought to do something like that, i also tried to cut my matrix into 4 submatrix, and store only the submatrix (which are sync with the big one)
      but i found these solutions a bit too tricky... :)
      G