How theitstreamer/stinger-studio works
Stinger Studio is a local desktop app for turning user images into OBS stinger transition files. The main workflow runs from the HTML interface through a Python bridge to the render engine, then lets the user save the result and use its transition-point timing in OBS. The README also describes presets, update checks, audio, logos, and batch rendering. The sampled source shows the bridge and parts of the engine; some UI and rendering internals are not shown, so those relationships are documented at the subsystem level.
Main entry points: engine.py Render engine · app.py Python API bridge · ui.html HTML interface
Components 15
Desktop interface
- HTML interface
ui.html - Python API bridge
app.py - Image and audio assets
app.py
Transition rendering
- Render engine
engine.py - Image preparation
engine.py - Style and layout
engine.py - Frame rendering
engine.py - Video encoding
engine.py
App services
- Presets and settings
app.py - Update check
app.py
Other components
- User
- Releases service
- FFmpeg
- Rendered output
- OBS
Connections 15
- User → HTML interface: configures
README.md - HTML interface → Python API bridge: calls API
app.py - Python API bridge → Image and audio assets: stores uploads
app.py - Python API bridge → Render engine: runs render
app.py - Python API bridge → Presets and settings: reads and writes
app.py - HTML interface → Update check: checks on startup
README.md - Update check → Releases service: checks releases
README.md - Render engine → Image preparation: loads images
engine.py - Render engine → Style and layout: builds layout
engine.py - Render engine → Frame rendering: renders frames
engine.py - Render engine → Video encoding: encodes output
README.md - Video encoding → FFmpeg: uses encoder
- Render engine → Rendered output: produces file
README.md - Python API bridge → Rendered output: saves file
app.py - User → OBS: uses transition
README.md