Striptease VS OctoWS2811

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.

I highly recommend the Teensy 4.x with the OctoWS2811 driver. This driver provides 8 channels of parallel output using DMA data transfers to offload the CPU. I think that meets your criterion for "hardware SPI". It doesn't seem like the T4 is overkill for what you're doing, especially if you're using floating point math. The T4 is blazing fast, and I've heard mixed reviews of ESP32 FP performance.

They are actually quite easy if you have some cash. Check out NeoPixel at Adafruit, they have a detailed guide on how you can control strip lights. NeoPixels are great but a tad expensive, you can find less expensive strips on discount resellers, search for “RGB Addressable LED Strip”. Some offer a control module but you will be limited the the built-in color patterns and speeds. If you can solder and program an Arduino you can modify example scripts to do a lot of things, even create digital signage and video walls.

Assuming you're going to use the OctoWS2811 library to drive the LEDs, the maximum possible frame rate for 2 channels of 1,008 LEDs should be:

However, if you have all 600 LEDs in a single strip, and the strip is WS2812, then you're limited by the internal refresh rate of the LEDs, which brings you to about 55hz. Which is ok, but if you spend much time in-between refreshs, maybe it's not fast enough. Certainly not for persistence-of-vision. If you're happy to break your strip into several sub-strips that get their own data line, you can speed up the refresh rate a lot. If you're using a Teensy 4, you can use this library for example, which allows you to efficiently drive many LED strips at once: https://www.pjrc.com/teensy/td_libs_OctoWS2811.html

You can also check out OctoWS2811 https://www.pjrc.com/teensy/td_libs_OctoWS2811.html

I've used RGBW for a number of projects involving non-addressable LED strips and spot lights. I haven't yet needed RGBW for a project requiring addressable strips, but it's in my tech roadmap. I no longer use FastLED, and I've written my own HSV/HSI-to-RGB/RGBW color conversion library. I use the OctoWS2811 library (not the adapter board) for DMA-based serial data output to addressable LED strips. It appears that this library supports RGBW strips, but I haven't tried it yet (others are doing the same). See the last few paragraphs of this article for more details.

But the OctoWS2811 Library can only use 8 Pins, at least on the page is only for a Teensy 4.0 and 4.1 the hint, that any group of pins is possible.