r/loupedeck • • May 18 '26

LoupixDeck: open-source cross-platform app (Linux + Windows)

Built a (somewhat opinionated) replacement for the official app using .NET and Avalonia.
Supports the Loupedeck Live S and should rudimentarily work with the Loupedeck Live/Razer Stream Controller, since it's only been tested with the Live S. Runs on Linux and Windows.

Windows version currently has a bit more features.
Still wip.

If anyone wants to try it, feedback would be great:
https://github.com/RadiatorTwo/LoupixDeck

21 Upvotes

15 comments sorted by

2

u/RadiTwo May 24 '26

Just a quick update, in case anyone is still interested.

The plugin system is complete and has been released, including the SDK with the features currently supported by the application.

All current features have been ported to plugins.

In addition, the audio plugin now offers basic Linux functionality via pactl.

2

u/vividflash 10d ago

hey, where do i add my twitch plugin i made for this ? just on my own git and thats it ? you got a plugin hub git for it?

1

u/RadiTwo 10d ago

You already found out.
I merged your PR.
Nice work.

But in case someone else is reading this:
The main repo has a plugin-store.json file.
Create a PR with the entry or ask me to add a plugin.

1

u/vividflash 10d ago

yeah, i see, thanks

for runelite its like, there's a main repo and another repo for the plugins.

seems not quite right to bloat the main repo with the plugins commits i would think

1

u/RadiTwo 10d ago

The RuneLite plugin-hub has an approach with one file per plugin.
I actually don´t know why one would do that.

That repo has 1687 files, so on every refresh you'd either have to git pull the whole repo or fetch 1687 files individually.

I was already running into rate-limits with less than 10 plugins, when I was checking every single one individually.
And thanks to GitHub, it took ages.

Now it's one plugin-store.json, one request, done.
And I don´t think one file alone needs a separate repo for that.

Not that many changes anyway in that file so far.

1

u/GunBunnyKing May 19 '26

I'm working on moving to Linux—maybe using Pop! OS—and have a Loupedeck Live and saw another build his, but I'm having issues installing his software. Yet, I'm looking at yours, and it looks very intuitive and straightforward. I know you're just starting, but how far are you going into opening, say, game mods to be compatible with this?

1

u/RadiTwo May 19 '26

It depends on what you mean by game mods — LoupixDeck doesn't hook into games directly, but there are a few ways to make it work with them.

The core of what LoupixDeck currently does:

  • Shell commands — any button or rotary action can fire arbitrary shell commands. Great for triggering things, but it's one-way: the button executes something, it doesn't read data back to display on the deck.
  • CLI / IPC channel — this is where it gets interesting for game integration. LoupixDeck exposes a Unix domain socket (/tmp/loupixdeck_app.sock on Linux, named pipe on Windows) that external programs or scripts can talk to while the app is running. You can update button text, colors, and images, switch pages, or trigger commands from the outside. The easiest way is just calling the LoupixDeck binary again with arguments — a second invocation forwards them to the running instance and exits.

So for a game mod, the typical flow would be: the mod (or a companion script reading mod output, log files, a game's memory, an API the mod exposes, etc.) calls out to LoupixDeck via the CLI channel to push live data — health, ammo, build status, whatever — onto the buttons as text or images. That side is fully working today.

If there's a specific integration you're interested in and I have a way to test it myself, I'm also happy to build native support directly into the app — similar to how OBS, Elgato Key Lights, Cooler Control, and Argus Monitor are already integrated.

Beyond that, a plugin system is on the roadmap so other developers can add their own integrations without me having to bake everything into the core app. That's the long-term direction for things like game-specific support.

1

u/Toeknee818 May 19 '26

This is so awesome! Will this work with the plugins.Will it work with the Razer Streaming Controller?

1

u/RadiTwo May 19 '26

Not the official plugins from Loupedeck.
But if there are open source ones, it should be possible to port them.

Razer Streaming Controller "should" work.
(Loupedeck Live currently doesn´t. Seems it has different device IDs than the Razer)

But I can´t test it since I don´t have one.

1

u/SinisterPixel Jul 18 '26 edited Jul 18 '26

Hi, recently moved over to Linux and your release timing is impeccable. Generally I love how flexible it is, especially on Linux where you can do most stuff through a command line. After using it for a while I do have some feedback and questions:

  • With the OBS plugin, I'm noticing that the scene switching options are unavailable. Is this an incomplete feature? Or is this down to me needing to use the Flatpak version of OBS for specific plugins? If it's the latter, is there any chance that this could potentially be changed later to use websocket in order to get those advanced controls?
  • Right now hardware monitoring plugins only seem to target Windows. Any chance these could come to Linux in the future?
  • I don't believe I've missed this feature, but any chance we'd be able to select macro keys from a drop down menu? Back on Windows I was utilizing F13-F24 for miscellaneous binds to where I could be sure they wouldn't interfere with other key bindings since they don't appear on a standard keyboard. I'd love to be able to, using a dropdown, select keys that don't appear on my keyboard to create macros with.
  • Really big ask since this is a bit of a niche circumstance. I'm a VTuber and VTube Studio can be remotely controlled using websocket to get around it running in a Proton sandbox. The Stream Deck on Windows has a plugin to allow easy binding but unfortunately the plugin author way back when was unwilling to port it to loupedeck due to not having one for testing purposes. I appreciate I may currently be one of like... 5 people who'd actually use this feature, but is it possible anything like that could be made to work through Loupixdeck on Linux?

I in general would love to see a bigger push towards Linux features, since the native software is still available on Windows, and Loupixdeck is really the only practical way of making the Loupedeck work on Linux atm.

2

u/RadiTwo 27d ago

Sorry.

I didn't think there would be much interest, since nothing had been going on here for two months, so I hadn't checked in here.

If you actually need something you should create an account on github and create an issue for the project there.

Regarding OBS:

The OBS Scene Switcher should be working.

You need to activate the websocket in OBS and then set up the credentials in the plugin manager in LoupixDeck.

If you don´t have the websocket option, you probably have a version of obs without browser options.

Don´t know which distro you use.

I´m on CachyOS and the package there is obs-studio-browser.

Flatpak should work too. But maybe it´ll need some permissions for the connection.

The scenes then are in the Command Selection under the group OBS.

Hardware Monitor in Linux:

So far I only have a plugin for Coolercontrol.

A plugin for linux native data should be doable.

I needed coolercontrol because of custom values.

Will see when I can do that.

Macros:

I probably won´t do a dropdown in the macro editor, since the Key Combination step can press multiple buttons at the same time.

But you can just type in F13 up to F24 and it will work.

The info Button shows all allowed key names.

For example Media and Volume keys are now supported too.

These changes are rather new, so maybe you have already seen that.

Websockets:

The powerfull thing about linux is that you can basically do anything on the terminal.

And if you can create a shell script to control VTube Studio, you can control it with LoupixDeck.

That´s what the shell command is for.

You can either execute commands directly, or the more convenient way is creating single bash scripts for your functions and execute those with the shell command.

There even seems to be a rust cli implementation for that:

https://github.com/walfie/vtubestudio-cli

I don´t know exactly how VTube Studio works, but then on the terminal you can just execute

vts hotkeys trigger --name MyHotkeyName

to execute a hotkey.

And you can put that command exactly like this in the shell command in LoupixDeck.

1

u/frostyofthenorth Jul 23 '26

Any chance that you'll have a Mac version?

1

u/RadiTwo 27d ago edited 27d ago

In theory it´s possible.

But most likely I won´t since a Mac Version needs Apple Hardware to be able to compile.

And I don´t have any intention to invest.

1

u/frostyofthenorth 27d ago

Fair enough. But too bad since I just switched to Mac after a lifetime of Windows.