I wanted a cheap, low-power, always-on person detector. Of course, I’m building this on a BrightSign XT5 player (more on that later). But since a friend said he was using a Beelink SER9 with a AMD Ryzen AI NPU (~50 TOPS) I thought I’d check it out. Can it actually run the detector? Short answer, as of today: no — and the reason is not the part you’d expect.
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.
In recent years, digital signage has become a solved problem: push content to screens reliably, at scale, on schedule. That’s not enough anymore. The market is now demanding screens that perceive — that understand what’s in front of them and respond in real time. Most of the hardware deployed in the field today will fail at that job because the foundational assumptions are wrong. Here’s what’s actually required and why the infrastructure choices you make now will define your deployment for the next decade.