diff options
| author | yum <yum.food.vr@gmail.com> | 2025-10-13 19:17:26 -0700 |
|---|---|---|
| committer | yum <yum.food.vr@gmail.com> | 2025-10-28 17:19:35 -0700 |
| commit | c3fa121f1a3ec74c5980bc8981e4836ca3a708f2 (patch) | |
| tree | 9a481e6d5a25ea59055724fb089ceeca43a00f42 /README.md | |
| parent | 8aca05a7e644f3d4aff6bcf636514882dd2ae934 (diff) | |
shart attack
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -4,11 +4,11 @@ Shitty service to proxy data from OBS into a low-latency MPEG-DASH stream VRChat 1. Configure OBS with a custom server pointing at `rtmp://<your-domain>/live` and the pre-shared key stored in `STREAM_PSK`. 2. Start the Python service (see `etc/systemd/system/obsproxy.service` for a sample unit). -3. Share `https://<your-domain>/dash/manifest.mpd` with your VRChat video player. Multiple viewers can consume the feed concurrently. +3. When the service starts it prints a session-specific manifest URL like `https://<your-domain>/dash/<session-hex>/manifest.mpd`; share that exact URL with your VRChat video player. Multiple viewers can consume the feed concurrently. Environmental knobs: - `STREAM_PSK`: required PSK for the single ingest client. - `DASH_SEGMENT_TIME` / `DASH_FRAGMENT_TIME`: tweak DASH segment/fragment durations to balance latency vs resilience. -The server seeds a fresh 128-bit session ID on every restart and writes DASH fragments under `<STREAM_DIR>/live/<session-hex>`. The public manifest route stays fixed at `/dash/manifest.mpd`. +The server seeds a fresh 128-bit session ID on every restart and writes DASH fragments under `<STREAM_DIR>/live/<session-hex>`. The manifest and segments are only exposed under `/dash/<session-hex>/`, making it infeasible to guess a live session path. |