I'm trying to adapt a Conway's game of life patch for use with my Monome 256. I've been sending coordinate dumps from a 16x16 matrixctrl object directly to the Monome, but it can't handle 256 led state updates at the same time. In order to remedy the problem, I would need to send only crucial updates to the Monome, meaning I have to filter out all redundant coordinate messages every time there is a matrixctrl dump.
Is there an efficient way to compare two states of a matrixctrl object (essentially, two different sets of 256 coordinates) to eliminate redundancies? For example, if the previous iteration had the button in the 4th column, 5th row turned off (4 5 0), ensure that the next batch of data did not send (4 5 0). I tried the zl.compare object, but I didn't get very far without a good way to delay the comparison of the two batches.
Thanks in advance!