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.
Illustration of the SceneDeck interface. Figures are representative, not a live feed.
The idea
Two machines, one link.
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. A built-in guide walks through setting
that link up, and through trimming the deck down to the scenes you actually switch to.
Your machine
SceneDeck
Coding, presenting, playing. Nothing is being encoded here.
obs-websocket 5.x
commands
scenes · audio · telemetry
127.0.0.1:4455
Streaming rig
OBS StudioREC
Capturing and encoding. Busy, and left alone.
to Twitch · YouTube · RTMP
Same machine works too — point SceneDeck at localhost and it behaves the same way.
The link is not limited to one client either: a co-host or moderator can run their
own copy of SceneDeck against the same rig, over a VPN or SSH tunnel, and switch
scenes or ride the mixer right alongside you.
Four things that break a stream.
01
The alt-tab tax
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.
02
A scene list out of control
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.
03
Fighting audio mid-stream
The input you need to mute is nested three scenes deep, and the slider you must
not touch is sitting right next to it.
04
Flying blind
Frames are being dropped somewhere, and you will find out from chat.
01 / Live & Inventory
Only the scenes you actually switch to.
Tag scenes by role once. The Live page then shows only your primary scenes, as cards,
with your own accent colour behind each one. A click goes straight to Program in direct
mode; in Studio mode it selects Preview, ready for Take. No renaming or restructuring.
Live · Primary scenes · Direct-mode demo
Program: Main Cam
Scene accent colour
Six roles, stored on your machine
Primary, Secondary, Module, Raw, Debug and Archive. Roles live in SceneDeck's own
local registry — your OBS scene collection is never touched.
Primary Live-switchable program scene
Secondary Valid scene, hidden from Live by default
Module Reusable nested building block
Raw Source wrapper — a leaf in the graph
Debug Temporary, never on a live path
Archive Preserved, out of the workflow
Set it up once
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
Flying blind is a choice.
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.
Streaming bitrate (kb/s)6000Average frame render time (ms)3.4
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
The mixer follows the scene.
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.
It reaches into nested scenes
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.
The lock is the point
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
See what is inside what.
Graph
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
Doctor
The Doctor page runs structural diagnostics across your scene roles and your scene
dependency structure, and tells you what it found.
Every scene in the registry still exists in OBS
A scene in the collection has no assigned role
A Primary scene nests a Debug scene
Dependency cycle detected between two scenes
No Raw scene nests another scene
Each finding carries a suggested fix
05 / Settings
Your rig, your rules.
Connection
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
Appearance
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.
Studio Purple
Nord
Dracula-inspired
Stream Red
Solarized Dark
Ubuntu Violet
While connected
Switch OBS profiles and scene collections straight from the SceneDeck header. Start
and stop streaming and recording from Live's compact output bar, alongside
replay buffer and virtual camera. Open Sources from the topbar for detailed inputs.
Internationalised with Fluent · English is the fallback locale
Show workflows in current source builds
Keep separate workspaces for saved OBS connections and scene collections.
Search tagged scenes, save named decks, pin actions, and open the command
palette with Ctrl+K. Review audio presets before applying them, run a preflight
check, and keep persistent health warnings visible while operating.
Add timestamp bookmarks and optionally retain session reports with CSV or
JSON export. Desktop shortcuts are opt-in and require a supporting desktop
portal. See the current user guide
for scope, timing and confirmation details; release downloads may lag source features.
Output safety
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.
Start confirmations off by default · Stop confirmations on
The real thing
Screenshots.
These native captures show an earlier release connected to OBS 32.1.2.
The current scene wall, Sources view and responsive Inventory list are documented in
the repository; these gallery assets and the HTML demo await a redesign refresh.
Live — scenes, outputs and the audio for the active sceneInventory — assign roles, export the registry as YAMLSettings — connection, and the output confirmations
One binary. Native GTK4.
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.
Language
Rust 2021
Toolkit
GTK4 + libadwaita
Licence
MIT
Architectures
amd64 · arm64
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.
Choose Snap, a published download for amd64 or arm64, or a source build.
Flatpak bundles are optional and are not available in every release.
Download commands below use amd64 filenames; on arm64, use the filename you downloaded.
Install from the Snap Store
The shortest path, and the one that keeps itself up to date.
$ sudo snap install scenedeck
To let SceneDeck save your OBS password in the desktop Secret Service keyring, connect its non-auto-connected permission:
If saving still fails, unlock your desktop keyring and check that a Secret Service is running. Passwords are not stored in the config file.
Install the Flatpak bundle
Optional GNOME-runtime bundles. Download a bundle first, then install it locally.
Your Flatpak installation also needs Flathub and the matching GNOME runtime.
No AppImage is published for this release. See the release page or choose another method.
Download the AppImage for your architecture, mark it executable, then run it.
Use delta updates only when the release also includes matching .zsync files.
No binary is published for this release. See the release page or choose another method.
The bare executable, plus a .tar.gz if you would rather
have an archive. You supply GTK ≥ 4.10, libadwaita ≥ 1.4 and libdbus-1.
Published native binaries are built on Ubuntu 24.04; older distro ABIs are not guaranteed.
Needs GTK ≥ 4.10 and libadwaita ≥ 1.4 development libraries,
libdbus-1-dev (Debian/Ubuntu package name),
glib-compile-resources, and the Rust toolchain pinned in
the repository.
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.
28 or newer — the WebSocket server is built in from 28
Desktop
Linux with GTK ≥ 4.10, libadwaita ≥ 1.4 and libdbus-1; native release binaries target Ubuntu 24.04 or compatible newer ABIs
Connection
OBS WebSocket, 127.0.0.1:4455 by default
Password storage
The system Secret Service keyring
Does SceneDeck have to run on the same machine as OBS?
No — 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. The Help
page inside the app covers the whole thing: enabling the WebSocket server,
finding the rig's address, and opening the port in its firewall.
Do I have to rename or restructure my scenes?
No. Roles and accent colours are stored locally by SceneDeck. Your OBS scene
collection is untouched.
Where is my OBS password kept?
In your system's Secret Service keyring. It is never written in plaintext and
never stored in the config file.
Can I use my own colours?
Yes. There are built-in light and dark theme families, and you can point SceneDeck
at your own light and dark CSS files.
Can a moderator or co-host run SceneDeck too?
Yes — OBS's WebSocket server accepts more than one client, so a second person on
a second machine can point their own SceneDeck at the same Host, Port and
password and control the same rig. There is no per-person permission split: the
password grants full control, so only share it with someone you would hand your
own keyboard to, and avoid exposing the port to the open internet — a VPN or SSH
tunnel is the safer path for a remote collaborator.
Is it translated?
SceneDeck is internationalised with Fluent, and English is the fallback locale.
Translations are welcome.
Something is wrong.
Open an issue on
GitHub. This is a
single-developer project, and bug reports are read.