blinkstick-userspace-led-daemon VS Striptease

I stayed with OpenWRT for a number of reasons that basically boil down to familiarity and I wanted to keep my config that I had tweaked over the years andother things I had in my setup that I had going with OpenWRT (SQM, LXC containers with things like OpenHAB, VPN to work, some custom code I had developed, etc.) The big thing I wanted was more RAM and performance because of auxiliary services I tossed on there.

BTW, if you're using a Teensy 4.x you might be interested in my project.

I'm not aware of any general significance of DrawOneFrame functions. They don't invoke any particular FastLED behaviour. For projects where a variety of different effects can be presented, the author may choose to use C++ classes to provide a standard interface to initialise and display those effects. In my WavyDots sketch, that function name is a vestige of such a choice. The Aurora project does something similar. So does the Striptease project, but there the DrawOneFrame function is simply called loop.

Have you ever come across my project? Perhaps you might find some interesting ideas to borrow.

Hi, I faced the same problem in my project.

In my project I did something similar and created abstractions for composing virtual strips by joining, extracting a portion or reversing other virtual or physical strips. Have a look at the Strip API.

That's what I'm using in my project based on Teensy 4.1 + Audio shield for driving 6 channels in non-blocking mode and it works great!

I'm using it in my project for driving 6 channels (Teensy 4.x) without any problems.

If you plan to use the Audio shield in your project (as I do on mine), then two Serial ports won't be available (pins 8 and 20), leaving you with 3 and 6 serial ports available on standard pins.

I have developed a library/framework for this, and it allows decoupling the physical layout of your strips (up to six) from the logical layout.

Hi, have a look at my project. It's a library/framework for Teensy 4.x + Audio Shield.