Production Truck: Install and launch

Install and launch

Install Python 3.10+, OBS Studio and the application's Python dependency. Official OBS downloads: https://obsproject.com/download

From the extracted folder:

python3 -m venv .venv
.venv/bin/python3 -m pip install -r requirements.txt
.venv/bin/python3 app.py

Windows equivalents: py -3 -m venv .venv, .venv\Scripts\python.exe -m pip install -r requirements.txt, then launch.bat. Mac can use launch.command after setup. The UI opens at http://127.0.0.1:8877. Alternative options: --port 8878, --data-dir /path/to/config, --no-browser.

For an existing or remote OBS workspace, enable its WebSocket server with authentication, then enter the address and password in Engineering → Existing / remote OBS engine. In managed Linux kiosk mode this is configured and connected automatically. The usual local address is ws://127.0.0.1:4455. This app speaks the OBS WebSocket v5 protocol. It enables Studio Mode; do this before a production. A remote engine needs verified WSS, so plain credentials are not sent across a LAN.

Sources are decoded, mixed, recorded and streamed by OBS, including camera audio. Install the supported NDI/DistroAV plugin for NDI reception. Network source support depends on the installed OBS/FFmpeg build and sender codecs. Check every camera before going live. Source creation does not overwrite existing inputs. Hub scene imports may require platform-specific text/source plugins; inspect them in OBS before use.

Closing/reloading the browser or stopping this controller does not stop OBS outputs. Use the explicit End broadcast / Stop recording controls, or stop outputs in OBS. The app reconnects automatically after restart; check the actual OBS state before retrying output commands. Output controls use explicit start/stop commands, not ambiguous toggles.