DEV Community

Cover image for Rescuing the Loupedeck: how we brought LoupixDeck to the Mac
Craig Lawson for Web-Engineer

Posted on Originally published at web-engineer.co.uk

Rescuing the Loupedeck: how we brought LoupixDeck to the Mac

On the corner of our desk sits a Loupedeck CT: a slab of knobs, buttons, touch keys and a big centre wheel. It's a lovely bit of hardware, and for a while it was close to becoming a very expensive paperweight. It's now one of the most useful tools we own, thanks to an open-source project called LoupixDeck. We've ended up contributing quite a lot to it.

A brilliant controller with a software problem

Loupedeck started in Helsinki, building hardware consoles for photo and video editing that grew into general-purpose controllers for streamers and creators. Logitech acquired Loupedeck in July 2023.

In our experience, the software was never the best part of the package, and it didn't get lighter after the acquisition. Each update felt heavier, and for a control surface that should simply respond the moment you touch it, that matters.

Then, in March 2025, Loupedeck announced it would no longer sell the Loupedeck product line, switching its focus to Logitech's MX Creative Console. It said support for existing devices would continue, and that the two products share a backend from software release 6.0. Support for the legacy 5.8 software and its marketplace ended on 30 March 2026.

If you own a Loupedeck Live or CT, the direction of travel is clear. The hardware's future is now in someone else's roadmap.

Enter LoupixDeck

{.img-right}

LoupixDeck is an open-source alternative to the official software, created and maintained by RadiatorTwo. Its own site sums it up neatly: "Your control deck. No vendor software." It's MIT-licensed, built in C# with .NET 10 and Avalonia, and supports the Loupedeck Live, Live S and CT, along with Razer's Stream Controller and Stream Controller X.

It does what a control deck should do, without the weight:

  • Profiles, pages and nested folders
  • A visual macro editor
  • Pages that switch automatically with the active application
  • A command-line interface and socket automation, so other tools can drive it
  • A virtual device mode for testing without hardware
  • A plugin system with a built-in Plugin Store and a public SDK

It started life on Windows and Linux. That's where we came in, because at Web-Engineer we work on Macs.

Bringing it to the Mac

We opened our first pull request for macOS support on Apple Silicon in September. Porting a hardware tool to a new operating system is rarely one big change. It's lots of small ones:

  • Finding the device. On Linux, LoupixDeck discovers devices with udevadm. On macOS we walk the ioreg device tree instead, which reports vendor and product IDs in a different format and in different places.
  • Sending keystrokes. Macros need to type and click on your behalf. On macOS that goes through CGEventPost, and it needs the Accessibility permission. Without that permission, macOS drops the events silently, so the app has to check the permission and ask for it clearly.
  • Behaving like a Mac app. The menu bar should say "LoupixDeck", the Dock icon should appear only while the window is open, and the Command key should be labelled properly. {.img-right} Testing on a real CT turned up more work, so we also added support for the CT's centre wheel and its screen, and fixed the CT's side strips. Then came the kind of bugs you only find by using something every day. The serial port was being polled a thousand times a second, which wasted CPU while the deck sat idle. A device could stay blank after the computer woke from sleep. And a lost touch event could leave the grid stuck.

So far, more than 30 of our pull requests have been merged into the project. macOS support is still labelled an experimental alpha in the project's README, and that's fair. It hasn't had the same mileage as Windows and Linux yet. But it's the setup we use every day.

Official Mac builds from our cloud

Source code is only half the job. Most people want to download an app and drag it into Applications, not install the .NET SDK.

LoupixDeck releases often. We counted ten releases in three weeks in October. Building Mac packages by hand at that pace wasn't realistic, so we automated it. With every release, our own cloud infrastructure builds the macOS packages on Apple Silicon hardware we run ourselves, and publishes them straight to the official release on GitHub. We build both Apple Silicon and Intel versions, and as registered Apple developers we sign and notarise every one. That means macOS can check the app came from us and hasn't been tampered with, so it opens without being blocked as coming from an unidentified developer. So far our pipeline has produced 82 builds for the project. The DMGs sit next to the Windows and Linux builds on each release, and both the project's README and loupixdeck.com credit Web-Engineer as the sponsor of the macOS builds.

This is the same kind of CI and release automation we build for clients. Here it happens to be pointed at an open-source project we love rather than a client's product.

A batch of plugins

{.img-right}
Once the Mac side was running, we started writing plugins for the things on and around our own desks. So far we've published eight:

  • Claude: open Claude, quick entry, usage gauges and a live state key for Claude Code sessions
  • Slack: unread badges, huddles, status and Do Not Disturb across workspaces
  • Visual Studio Code: run commands, see problems, git and debug state on the keys
  • Mac Monitor: live CPU, memory, thermal, network and disk keys
  • Wacom: display toggle and precision mode for Wacom tablets on macOS
  • Govee: lights, colours, scenes and segments over the local network
  • TP-Link Kasa: smart plugs and power strips, with live on/off state
  • Anthem: receiver control, including volume, inputs, listening modes and Zone 2

Each one deserves its own write-up, and we'll cover several of them in future posts.

Why a web agency cares about a desk controller

It's a fair question. LoupixDeck touches a surprising amount of what we do day to day: cross-platform desktop code, low-level hardware communication, operating-system integration, plugin APIs, network-connected devices and automated build pipelines. That's a good reminder that "web agency" undersells it. A lot of our work sits behind the website: the integrations, infrastructure and tooling that make things just work.

It's also been a pleasure to work with an open-source maintainer who reviews quickly and cares about quality. Huge thanks to RadiatorTwo for building LoupixDeck and for welcoming our contributions.

If you've got a Loupedeck in a drawer, give LoupixDeck a try. The source is on GitHub. And if you've got a project that needs this mix of hardware, software and automation, get in touch. We'd love to hear about it.

Top comments (0)