but polyat can only address 128 leds per channel…
thats absolutely fine for the Linnstrument, which has very few ‘cells’
but, for the Erae, we have 24 x 42, so thats 1008 = 8 midi channels!
then it’d be very inefficient to write a large number of pixels…
e.g. consider a simple 4x3 border (filled) , that 12 pixels , so 48 bytes of (poly at = 4 byte message)
of course, sysex has a bit of an overhead, in this api, id say around 20 bytes… but once you start writing more than a few (5?) pixels, that going to be offset.
also the ‘pixels’ on the Erae are RGB, so a single 7 bit value (as used with poly AT) is not enough to to represent this.
so to handle this properly with polyAT, you have to start introducing the concepts of colour palettes, which would have to be defined by sysex anyway.
that said, I think a default set of 128 colours could be chosen that would be reasonable in most cases.
so for many cases you’d not need this - I guess
anyway, Im sure Embodme could do it, if there was a demand…
but I personally am happy enough with sysex - the approach they have chosen seems to be much more suited for more general purpose application - and I think scales better.
but for sure, I can see some might think polyat messages are easier to deal with if you’re not used to using sysex, or using some kind of environment that doesn’t deal with sysex nicely.