Profile cover photo
Profile photo
Mark Kriegsman
I make things, e.g., Veracode, FastLED, and trouble.
I make things, e.g., Veracode, FastLED, and trouble.

Communities and Collections

FastLED 3.1.8 released: minor updates, bug fixes, and board-support improvements.
We've just released FastLED 3.1.8, collecting up a number of community contributions including: support for Adafruit Circuit Playground Express, Gemma, Trinket m0, ATmega328 non-'p', PJRC's WS2812Serial driver, as well as a number of bugfixes and small improvements to ESP32 support and Makefile-based compilation. Thanks to the FastLED community for your support and enthusiasm, and thanks especially to all the contributors -- we've thanked them by name in the release notes!
Find the update in on github, or through the Arduino Library Manager, and enjoy.
(We skipped 3.1.7 just due to internal housekeeping, you didn't miss one; hopefully the 3.1.8 release is clean.)

Post has attachment

Released: FastLED 3.1.6, including support for ESP32 and Teensy 3.6

Hi, all. Thanks to a great deal of help and contributed code from many members of our community, we're pleased to announce the release of FastLED 3.1.6, which includes support for the ESP32, Teensy 3.6, the ATtinyX41, and the OctoWS2811 adapter board. In addition, this release collects a number of bug fixes, as usual.

Thank you again to everyone who shares their time and energy with the FastLED community. Special thanks to Jason Coon, Paul Stoffregen, Rina Shkrabova, Sam Guyer, and Limor "Lady Ada" Fried for their code commits in this release.

The latest code and releases are available on Github, in the usual place: and

Personal announcement, and a request
Dear FastLED friends,
About a week ago, +Daniel Garcia and I lost a close and beloved family member, without warning, at age 40. We are devastated.
Many people who have known have reached out to ask how they can help offer support in this terrible time, and we're blessed to have so much love and support in our lives.
While Dan and I are trying to make sense of any of this, and grieve, I'd like to ask that you, the good people of the FastLED community, help us by helping each other a little bit extra while we step away for a bit. I love how much the members of this community have always helped and supported each other, and all I ask now is that you keep doing exactly that: support each other. Be helpful, and patient, and playful, and warm. Dan and I are still 'here', but right now we need to ask the rest of the community to take care of each other while we step away to handle our terribly sad loss.
Thank you for understanding and sympathy, and for helping each other so much, as you always have. And today, right now, reach out to someone you haven't spoken to in a while, and tell them you love them.

Post has attachment
Just call me Ranger LED Program.

Post has attachment
When you bury LEDs in the ice, with the beer.
(Foreground bottle: "I Love Lamp" from Evil Genius Brewing Co.)

Post has attachment
Five years ago today, I lit up my first LED art gear. I wrote a little bit about it here: "If something intrigues you, step toward it."
Frostbyte lives
Frostbyte lives
Add a comment...

Post has attachment
Boston is expected to get a good dose of snow over the next day, and I can't resist laying down some lights shine up through the snow. Here's what they look like just lying on top of the existing snow. Hopefully tomorrow night I can post a second video showing what they look like with the new snowfall on top. ( < 1min)

P.S. "IP68" FTW.

Post has attachment
Exploring a spherical pixel layout idea...

Change to 'noise' functions
So this is awkward: I finally found and fixed an integer overflow/underflow bug that had been lurking in the FastLED 'noise' functions for a long time. Before, due to the internal math overflow, the noise functions could sometimes produce significantly 'discontinuous' output, like:
21 22 24 26 172 173 174 175 (for example)
With the new code change in place, the output is more or less 'continuous', like:
21 22 24 26 28 30 31 32 33 33 (for example)

While this is definitely a bugfix, bringing the code much more closely in line with how it was designed and intended to behave, it could also result in a significant change in the appearance of your existing animations if they use the noise functions.

But if you want the old behavior, you can have it. Locate the file "fastled_config.h", and uncomment the line that says
With that line uncommented, the noise functions will revert to their old behavior -- including the discontinuities, which you may have used in some advantageous way in your animations.

These changes are, at present, found only in the latest version of the master branch on github.

Sorry if this disrupts your work, or requires you to change the flag for existing animations.

We try pretty hard not to make changes that aren't backwards-compatible, and this one was a tough call. There's no one right answer here, so we changed the code to the 'new' (correct, intended) way, but provided a flag for you to stick with the old way if you so desire.
Wait while more posts are being loaded