OBS STUDIO · TWITCH · TWO-MACHINE SETUP
Your stream. Your terminal. Zero alt-tabs.
Five small, sharp, open-source utilities for OBS Studio and Twitch — built in Rust and Crystal, terminal-first, no Electron in sight.
- RUST + CRYSTAL
- SINGLE BINARIES
- NO ELECTRON
- OBS-WEBSOCKET 5
- TWITCH IRC
- MIT LICENSED
THE IDEA
Two machines, one link.
OBS runs on the rig that captures and encodes. These tools run 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.
YOUR MACHINE
obsctl-rs ▸ dashboard
● connected · obs 30.1 · 60 fps
▶ LIVE: Gameplay
scenes: intro · gameplay · brb
mic −12 dB ▮▮▮▮▯▯ · desktop −20 dB
$ obsctl scene switch BRB
{ "ok": true, "scene": "BRB" }
$ obsctl stream status
{ "live": true, "kbps": 6000 }
exit 0
CPU34%
FPS60.0
ENC2.1ms
NET0 DROPPED
viewer_42: gg that transition
mira: !uptime
twi-bot: live for 2h 14m
you: thanks <3
OBS-WEBSOCKET 5.X
COMMANDS ▸
◂ SCENES · AUDIO · TELEMETRY
127.0.0.1:4455 BY DEFAULT
STREAMING RIG
CAPTURING AND ENCODING.
BUSY, AND LEFT ALONE.
— TO TWITCH · RTMP
BUSY, AND LEFT ALONE.
— TO TWITCH · RTMP
THE MAP
click any node
OBS-WEBSOCKET 5.X
COMMANDS OUT ▸
MONITOR
◂ SCENES, AUDIO, TELEMETRY
RTMP ▸
CHAT · IRC
CAPTURES SCREEN + AUDIO
WORKSTATION — WHERE YOU SIT
STREAMING RIG
SAME MACHINE WORKS TOO — POINT THE TOOLS AT LOCALHOST (127.0.0.1:4455 BY DEFAULT) AND EVERYTHING BEHAVES THE SAME WAY.