OBS Studio remote · Native Linux · v0.1.21
SceneDeck is a native GTK4 control surface for OBS Studio. Scenes, audio and live telemetry for your whole session — driven from the computer you actually work on.
$ sudo snap install scenedeck
Illustration of the SceneDeck interface. Figures are representative, not a live feed.
The idea
OBS runs on the rig that captures and encodes. SceneDeck runs on the machine you actually work on. Between them is OBS's own WebSocket server — so the machine under load never has to be the machine you touch.
Coding, presenting, playing.
Nothing is being encoded here.
obs-websocket 5.x
127.0.0.1:4455
Capturing and encoding.
Busy, and left alone.
Same machine works too — point SceneDeck at localhost and it behaves the same way.
Your rig runs OBS. You run everything else — the code, the deck, the game — on a different machine. Every scene switch costs you a context switch.
Real setups fill with utility scenes, camera-only scenes, overlays and source wrappers. Things that belong inside other scenes, and should never be clicked live by accident.
The input you need to mute is nested three scenes deep, and the slider you must not touch is sitting right next to it.
Frames are being dropped somewhere, and you will find out from chat.
01 / Live & Inventory
Tag scenes by role once. The Live page then shows only your primary scenes, as cards, with your own accent colour behind each one. One click sends a scene to program. No renaming your collection. No restructuring it.
Live · Primary scenes
Program: Main Cam
Scene accent colour
Primary, Secondary, Module, Raw, Debug and Archive. Roles live in SceneDeck's own local registry — your OBS scene collection is never touched.
Inventory is where you tell SceneDeck what your scenes are for. Assign a role, assign an accent colour, and drag them into an order that sticks — that order is the order the Live page uses.
Export and import the whole registry as YAML
02 / Stats
The Stats page is a live instrument panel for your OBS session — gauges and charts, updating while you work, on the machine that is not busy encoding.
It reflows. The Stats page rearranges for narrow windows, so it still works parked in a column beside your editor.
And it never leaves. Connection state, stream and record status, FPS, streaming bitrate, OBS CPU usage and dropped frames sit in the status bar on every single page.
Figures on this page illustrate the Stats layout. They are not a live feed.
03 / Mixer
Global audio first, then every audio-capable input in the active scene — including inputs nested inside other scenes and groups. Mute instantly. Ride levels on compact vertical sliders. Lock a slider so you never nudge it on air.
The Mixer is a page of its own, with three modes: Active follows the OBS program scene, Selected inspects a scene without following OBS, and Pinned holds one scene no matter what goes to program.
If an input is buried inside a scene that is itself inside your program scene, it still shows up in the mixer. You do not have to go find it.
Locking a card freezes its slider locally. The fader stops responding to pointer and keyboard, so the one level you must not touch cannot be touched.
Try the lock on any channel
04 / Graph & Doctor
The Graph page draws your nested scene dependencies — which scenes are embedded inside which. The collection you have been building for eighteen months, as a diagram, in one screen.
Directed edges — a parent scene nesting a child scene
The Doctor page runs structural diagnostics across your scene roles and your scene dependency structure, and tells you what it found.
Each finding carries a suggested fix
05 / Settings
Point SceneDeck at your OBS host and port — 127.0.0.1:4455
by default — and connect. Your password is stored in the system Secret Service
keyring. Never in plaintext, never in a config file.
Stored in the system keyring
Follow the system colour scheme, or pin light or dark. Choose a built-in theme family, or point SceneDeck at your own light and dark CSS files.
Switch OBS profiles and scene collections straight from the SceneDeck header. Start and stop streaming and recording from the sidebar, on any page.
Internationalised with Fluent · English is the fallback locale
Going live and stopping a recording are the two clicks you cannot take back, so each of the four output actions can ask first. Turn the confirmations on or off independently — start stream, stop stream, start recording, stop recording.
Off by default for recording, on for the stream
The real thing
The actual application, connected to OBS 32.1.2. Everything above this point is a rebuild in HTML so it can theme with the page; these are not.
SceneDeck is a single small Rust binary built with GTK4 and libadwaita. It looks and behaves like the rest of your desktop because it is built with the same toolkit your desktop is.
One GTK main thread owns every widget. A Tokio runtime owns every OBS WebSocket call. Events cross back over an mpsc channel, polled every 50 ms. That boundary is why the interface does not stutter when the network does.
06 / Install
Five ways in, on both amd64 and arm64. All of them are one command.
The shortest path, and the one that keeps itself up to date.
$ sudo snap install scenedeck
Built against the GNOME runtime and published with every release.
$ flatpak install --user ./scenedeck-0.1.21-linux-amd64.flatpak
$ flatpak run io.scenedeck.app
Nothing to install. Delta updates are available through the published
.zsync files.
$ chmod +x scenedeck-0.1.21-linux-amd64.AppImage
$ ./scenedeck-0.1.21-linux-amd64.AppImage
The bare executable, plus a .tar.gz if you would rather
have an archive. You supply the GTK4 and libadwaita runtime libraries.
$ chmod +x scenedeck-0.1.21-linux-amd64 && ./scenedeck-0.1.21-linux-amd64
Needs the GTK4 and libadwaita development libraries,
glib-compile-resources, and the Rust toolchain pinned in
the repository.
$ git clone https://github.com/worxbend/scenedeck
$ cargo build --release
Every archive is published on the GitHub Releases page for v0.1.21.
07 / Terminal
SceneDeck is a GTK4 window. If you would rather stay in a terminal, these are separate tools from the same author — three of them talk to the same obs-websocket 5.x server SceneDeck does, and one keeps your chat off a browser tab.
A btop-style terminal dashboard for OBS: live CPU, frame pacing, encoder health, outputs, scenes and audio.
worxbend.github.io/obs-statsA local OBS Studio controller in the terminal — the same job as SceneDeck, without leaving your shell.
worxbend.github.io/obsctl-rsCLI and TUI for driving OBS through obs-websocket — scriptable, so it fits in a hotkey or a deploy step.
worxbend.github.io/obsctlTerminal-native Twitch chat. Read and send, switch channels and watch raids without a browser tab open on your streaming rig.
worxbend.github.io/twiEverything else is on github.com/worxbend.
Spec sheet
127.0.0.1:4455 by defaultNo — that is the point. Run OBS on your streaming rig and SceneDeck on whatever you are actually working on, and point it at the rig's host and port.
No. Roles and accent colours are stored locally by SceneDeck. Your OBS scene collection is untouched.
In your system's Secret Service keyring. It is never written in plaintext and never stored in the config file.
Yes. There are built-in light and dark theme families, and you can point SceneDeck at your own light and dark CSS files.
SceneDeck is internationalised with Fluent, and English is the fallback locale. Translations are welcome.
Open an issue on GitHub. This is a single-developer project, and bug reports are read.