qumo ships v0.4.0
Highlights 🎮 Playground — one-command local demo qumo playground starts a self-contained demo: an in-process relay + embedded web UI at http://127.0.0.1:8080. No cert setup, no Vite, no separate relay — just one binary…
Repository Snapshot
- Repo: qumo-dev/qumo
- Source: GitHub
- Language: Go
- Last pushed: 2026-07-22
- Milestone: Release
v0.4.0 - Published: 2026-07-08
Summary
Highlights 🎮 Playground — one-command local demo qumo playground starts a self-contained demo: an in-process relay + embedded web UI at http://127.0.0.1:8080. No cert setup, no Vite, no separate relay — just one binary…
Why It Matters
qumo-dev/qumo is an active MOQ implementation, so a tagged GitHub release is a concrete milestone for implementers tracking protocol and deployment progress.
Source Excerpt
Highlights 🎮 Playground — one-command local demo qumo playground starts a self-contained demo: an in-process relay + embedded web UI at http://127.0.0.1:8080. No cert setup, no Vite, no separate relay — just one binary. Supports Webcam (camera/screen round-trip), RTMP push, RTSP push, and IP Camera (RTSP pull) scenarios from the browser. 📹 RTSP support (push + pull) qumo rtsp-push (formerly qumo rtsp) — accept RTSP push streams from ffmpeg or encoders (ANNOUNCE/RECORD server) and republish as MoQT. qumo rtsp <url> — pull RTSP directly from an IP camera (DESCRIBE/SETUP/PLAY), with Basic + Digest auth, TCP-interleaved transport, and automatic reconnect. 🔧 initData — browser-decodable ingest Ingested streams (RTSP/RTMP) now carry codec initialization data as Base64 initData in the MoQT catalog — AVCC SPS/PPS for H.264 video, AudioSpecificConfig for AAC audio. This is the same sh…