Yep, the trick here is that Pixelblaze doesn't store or stream pixel data, the patterns are small fast programs that generate pixel data on the fly.
One benefit of this approach is that Wifi can drop or be unreliable without impacting animations.
This also lets them react to inputs e.g. using some of the IO or ADC, or using the sensor expansion board for audio, light, or movement (accelerometer). Each pattern is typically 5-15K (this includes compressed source, compiled, and preview animation), and there's plenty of flash to store hundreds of different patterns.
One benefit of this approach is that Wifi can drop or be unreliable without impacting animations.
This also lets them react to inputs e.g. using some of the IO or ADC, or using the sensor expansion board for audio, light, or movement (accelerometer). Each pattern is typically 5-15K (this includes compressed source, compiled, and preview animation), and there's plenty of flash to store hundreds of different patterns.