mattias petersson

I'm experiencing strange things when sending the bang message to 

matrixctrl. I want to write x/y-values into 2 buffers via peek~ with 

matrixctrl as interface. This works as expected.

However, when i send the bang to matrixctrl it sends out its contents 

out the left outlet (as it should), and i thought that this would not 

change anything in the buffers, just re-write the same data that's 

already stored in it.. Instead it seems to erase the contents. And i 

really don't understand why. Then if i send the clear message to 

matrixctrl something happens with one of the buffers..

Maybe i did something wrong or it is a bug.

Any help would be great! Example patch below with steps to reproduce my 

I'm experiencing strange things when sending the bang message to 
matrixctrl. I want to write x/y-values into 2 buffers via peek~ with 
matrixctrl as interface. This works as expected.
However, when i send the bang to matrixctrl it sends out its contents 
out the left outlet (as it should), and i thought that this would not 
change anything in the buffers, just re-write the same data that's 
already stored in it.. Instead it seems to erase the contents. And i 
really don't understand why. Then if i send the clear message to 
matrixctrl something happens with one of the buffers..
Maybe i did something wrong or it is a bug.
Any help would be great! Example patch below with steps to reproduce my 
problem.
/m
---------



matrixctrl-bang-weirdness

i'm afraid your patch is wrong. try with a smaller matrixctrl. then 

it might be easier to read the printout after a bang. matrixctrl spits 

out all xy-pairs and as your patch is filtering one of the dimensions, 

values will be overwritten. you'll see this if you have an empty cell 

below an active one in the same column (eg col 4 row 2 is active but 

col 4 row 3 is not: [4, 2, 1] and [4, 3, 0]). if you ignore the row 

how to solve this depends on how you want to store the data. in your 

example you'd actually need 4 (or 8) buffers to save all data without 

some kind of mixdown/merge. perhaps using one 4-channel buffer?

On 04.09.2006, at 03:09, Mattias Petersson wrote:

> I'm experiencing strange things when sending the bang message to 

> matrixctrl. I want to write x/y-values into 2 buffers via peek~ with 

> matrixctrl as interface. This works as expected.

> However, when i send the bang to matrixctrl it sends out its contents 

> out the left outlet (as it should), and i thought that this would not 

> change anything in the buffers, just re-write the same data that's 

> already stored in it.. Instead it seems to erase the contents. And i 

> really don't understand why. Then if i send the clear message to 

> matrixctrl something happens with one of the buffers..

> Maybe i did something wrong or it is a bug.

> Any help would be great! Example patch below with steps to reproduce 

fredrikolofsson.com klippav.org musicalfieldsforever.com

hi mattias,
i'm afraid your patch is wrong.  try with a smaller matrixctrl.  then 
it might be easier to read the printout after a bang.  matrixctrl spits 
out all xy-pairs and as your patch is filtering one of the dimensions, 
values will be overwritten.  you'll see this if you have an empty cell 
below an active one in the same column (eg col 4 row 2 is active but 
col 4 row 3 is not: [4, 2, 1] and [4, 3, 0]).  if you ignore the row 
the first value will be overwritten.
how to solve this depends on how you want to store the data.  in your 
example you'd actually need 4 (or 8) buffers to save all data without 
some kind of mixdown/merge.  perhaps using one 4-channel buffer?
/f0

> I'm experiencing strange things when sending the bang message to 
> matrixctrl. I want to write x/y-values into 2 buffers via peek~ with 
> matrixctrl as interface. This works as expected.
> However, when i send the bang to matrixctrl it sends out its contents 
> out the left outlet (as it should), and i thought that this would not 
> change anything in the buffers, just re-write the same data that's 
> already stored in it.. Instead it seems to erase the contents. And i 
> really don't understand why. Then if i send the clear message to 
> matrixctrl something happens with one of the buffers..
> Maybe i did something wrong or it is a bug.
> Any help would be great! Example patch below with steps to reproduce 
> my problem.
> /m
> ---------
> max v2;
> 

   #|
      fredrikolofsson.com     klippav.org     musicalfieldsforever.com
   |#

matrixctrl bang weirdness