Most people think of a BrightSign player as a thing that plays - you load it with content, point it at a screen, and it pushes pixels. And yeah, if you’ve ever wired an RTSP camera feed into one, you know it’s a perfectly nice way to throw a live camera (or a few) on a wall. But that’s selling the box way short. There’s an NPU sitting in there, idle, and it can watch the room back.
I’ve written before about what a BrightSign extension actually is and about why edge AI has to run locally on signage. This post is the “show, don’t tell” follow-up. If you want to see what all that theory looks like as a running, watchable thing, there’s exactly one place to start: Argus.
Most people think of a BrightSign player as the little box behind a screen that loops a video. That’s true right up until you realize the thing is a full ARM64 Linux computer with an NPU sitting idle most of the day. And you can run your own code on it. Natively. That’s what an extension is, and once you grok it, a whole world opens up.
A short update on my whale song project: I fell down a few technical rabbit hole!
Tl/Dr: It’s on the network! But in my analysis, I fell victim to my own bias.
Picking up from last weekend, I play with the ESP32-POE-EA board from Olimex using the Espressif FreeRTOS ESP-IDF Framework.
Been awhile, head spinning, took some time to just play.