Output to multiple Teensy's or simialr, to drive APA102 strips

Hi there.
Trying to replace some Pixelpushers with Teensy’s to drive APA102 strips.
I have 32 frames which have 840 pixels each, driven by a PSU.
I now want to put a Teensy in each PSU box and run ethernet to each Teensy.
Previously I had 8 pixelpushers driving 4 frames each, but the wiring was a nightmare.

I’m getting a bit of help on the FASTLED subreddit on the hardware side, but wondering what the TD end will look like. Do I output serial data to each Teensy via ethernet?
Will each Teensy need it’s own node?
Serial DAT? Looking to get 60fps on each frame.

Previously I’ve used a custom app that takes a Spout output from TD, and sends the data to Pixelpushers. But I’m trying to contain all of the code within one TD patch now, so there’s not multiple apps open.

Any help greatly appreciated.
Also any insights on using Teensies/ ESP32s, Rpis etc with APA102 and TD>

Hi @lyallmarcus,

not really familiar with the Teensy but maybe there are some answers in this post here:

cheers
Markus

In case anyone finds this. I went a different route.
The issue was that APA102 strip is a pain, because most of it is in 5 volt form.
And the voltage drop with 5v tape is really tricky to manage.
The PSU has to be really close to the strip or the colour goes over long distances.

To build my piece, I have to go to 12v or 24v strips.
When you do this, the wiring for power and signal becomes much much easier.
And there are some really straightforward integrated boxes that you can just run Artnet into.
So the teensy dream is dead for the moment. We did get one working, but by the end of our testing, we concluded that 5v strips aren’t worth the hassle.

Now I have 500m of 5v strips in search of a new form factor.