Timeline for NeoPixel library performance: Adafruit vs. FastLED
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 17, 2018 at 7:40 | comment | added | Bogdan Stăncescu |
Fair enough, that makes sense. I had noticed that in practice the speed difference was barely noticeable – certainly nothing like the 4x difference the millis() data seems to suggest. I was just too lazy to actually rig up a separate clock to measure real user time. Thank you for taking the time to clarify this. Having said that, I did manage to squeeze a bit more speed out of it by removing the throttler altogether – and the LEDs didn't get borked.
|
|
| Jan 17, 2018 at 7:39 | vote | accept | Bogdan Stăncescu | ||
| Jan 16, 2018 at 1:44 | comment | added | rDg | Also - the rate throttler referred to above is to cap updating WS2812 leds at a rate no higher than 400Hz - WS2812 leds freak out if you update them more than 400 times/second. | |
| Jan 16, 2018 at 1:42 | comment | added | rDg | (Also - when it comes to WS2812 data on AVR, the Fast in FastLED is also for the writing data - the tuned assembly output takes exactly 30µs per pixel (1.25µs per bit, or 20 clock cycles on a 16Mhz avr), and in that 30µs, not only is it writing out data, but it's also doing the scaling/dithering/color correction for the led data to write out) | |
| Jan 16, 2018 at 1:34 | history | answered | rDg | CC BY-SA 3.0 |