So I was thinking about how matrix scanning might work for scrolling text, but I guess the Audulus scan rate on the light node is ~120hz. So I accidentally made a patch that demonstrates aliasing.
3x4 char seq.audulus (157.0 KB) FLICKER WARNING
The idea was to switch between characters so quickly that you see the whole thing as continuous. However, because the light node only checks for an input maybe 120 times a second, rates exceeding 60 Hz start to skip inputs. Patterns emerge as the inputs are scanned, the length of the sequence is changes as well as the rate. You even see fleeting glitches.
Mostly I felt like sharing, but It might be fun to better understand the underlying limitations of displays in Audulus.