Is it possible to run FastLED w/ ws2812B & the Teensy 3.1 audio board? Specifically, can I playback sound while updating LEDs? I get clicking sounds on FastLED.show() with FastLED 3.0, and FastLED 3.1 doesn’t light any LEDs (at least connected to the default audio board setup). In fact, trying to open the serial monitor causes the IDE to hang. I’d appreciate any tips in order to avoid running LEDs on a dedicated Teensy (much harder to sync visuals to audio stuff).
I suspect the audio library is running interrupts frequently and long enough to mess with the timing of the ws2812b on FastLED 3.1 or to cause clicks in the audio when writing the leds blocks interrupts on 3.0.
I would suggest switching to apa102’s which don’t need to mess with/block interrupts to be written at full speed, and in fact are faster than even 16 lines of parallel ws2812 would be.
Okay, thanks. I’m moving to apa102 permanently after this project, but this one needs to stay ws2812b. Guess I’m stuck with two boards.
The other possibility would be to use fastled’s octows2812 driver - you would just have a bunch of empty/unused led data in memory for it - but assuming there is no conflict between the pins used by the audio board and the pins used by octows2812 you should be fine.
See https://github.com/FastLED/FastLED/wiki/Parallel-Output for a rough reference.
I read that Paul Stoffregen ported his octows2812 library to be friendly with the audio library, but the audio board itself uses many of the pins required by octows2812. I don’t see how they’re compatible. I only need one pin for leds, whereas octows2812 seems hard coded to use several.