Why broadcast configuration is finally catching up with the way engineers actually think
Remember when computing meant typing commands into a black screen? You’d memorise arcane syntax, hope you hadn’t missed a slash, and pray that the blinking cursor wasn’t about to deliver an error message. Then Windows arrived. Suddenly, you could point at what you wanted. Click. Drag. Drop. It wasn’t just easier – it was fundamentally more aligned with how our brains actually work.
We organise things visually. We think in flows, in relationships, in spatial arrangements. The graphical interface didn’t just make computing more accessible; it made it more human.
So here’s a question: why did broadcast engineering spend the last decade going backwards?
The Configuration Dark Ages
For years, configuring broadcast infrastructure has meant navigating endless parameter trees, typing obscure commands, and wrestling with interfaces that looked suspiciously like they were designed by someone who missed the memo about the 1990s ending.
You wanted to route a signal through colour correction, then audio processing, then frame synchronisation? Excellent – here’s a wall of text fields, drop-down menus nested five levels deep, and a configuration language that looks a little like Swahili.
It was the DOS era all over again. But with more at stake.
Enter BLADE//planner
At NAB 2026, arkona unveiled something that feels, for broadcast engineering, like the moment we all switched from DOS to Windows. BLADE//planner is a graphical configuration tool that lets engineers design entire system architectures offline, through a visual interface that actually makes sense.
Instead of building workflows parameter by parameter, you simply route what you need and pick the services you want – Routing, Proc AMP, HDR-SDR conversion, audio mixing and DSP, video mixing and keying, delay and frame synchronisation etc. -by dragging and dropping them into place. The system shows you what you’re building, visually, in real time.
It’s not just a nicer interface. It’s a fundamentally different way of working. One that taps into how engineers actually think about signal flow: as a visual journey from source to destination, not as a spreadsheet of settings.
The Best of Both Worlds
Now, before any veteran engineer starts worrying that this means losing control, relax. BLADE//planner abstracts the complexity for operators who need to get things done quickly. But for those who want to get their hands dirty? Over one million controllable parameters remain accessible via an open API. Automate at scale. Configure with surgical precision. Build your own custom control systems on top of it. The choice is yours.
This is the philosophy that runs through everything arkona does and is informing every stage of our UI development, across all kinds of interfaces and architectures: give engineers the tools they need, in the way that suits them best. Whether that’s a third-party control system they already know, a custom solution they’ve built themselves, or the intuitive power of BLADE//planner itself.
The Only Catch
There’s always a downside. Here, it’s for those poor unfortunate developers who got into programming because they had visions of themselves as Keanu in The Matrix, Angelina Jolie in Hackers, or – heaven forbid – Hugh Jackman in Swordfish. We all know that for a good hacking scene there needs to be a wall of screens and furious tapping as lines of luminescent green code cascade down the monitor. It’s cinema gold. It builds tension.
Case in point, how oddly discordant was it when Lex – the girl in Jurassic Park – exclaimed ‘It’s a Unix system, I know this’, as she clunkily clicked through the various containers whilst dinosaurs hammered at the door? Realistic? Possibly (except the dinosaurs…). Suspenseful? Not really.
So, for anybody wanting to look cool whilst saving the world, BLADE//planner may prove to be something of a disappointment. It’s calm. It’s straightforward. Drag. Drop. Configure. Done. Not exactly the stuff of Hollywood thrillers. But then again, neither was Windows when it first arrived. And nobody in their right mind would go back to DOS.
But for those that actually want to get things done? It might just be the future. We hope we’ll see you at IBC 2026, so that we can show you exactly what we mean.
