Back to News
news

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…

Source: GitHubView source →

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…

One MOQ email every Monday

The week's changes, sorted and summarized: IETF draft revisions and working-group decisions, new releases from MOQ implementations, and streaming news. Every item in a sentence or two, with a link to the source.

Right now we're tracking DEMOQED 2026 — talk recordings get linked the day they're posted — and the run-up to IETF 127 in San Francisco, Nov 14–20.

Free. No spam, unsubscribe anytime.

Read before subscribing:Latest completed free issue

Go deeper with MOQ Edge Pro

Weekly deep-dives, IETF standards tracking, and streaming tech trend reports — from $9/mo.

See plans →

More from MOQ Edge

newsNov 21, 2026via GitHub

moq-wasm ships moq-wasm (Rust) 0.0.1

The first release of moq-wasm for Rust, as a git dependency on the rust-sdk-v0.0.1 tag, tested on Linux x86_64, Linux aarch64 and macOS arm64. The session offers draft-18, then draft-14. moq_wasm::connect opens a Sessio…

newsNov 20, 2026via IETF Mailing List

IETF MOQ WG: -02 of the ad creative signaling draft is posted

Steven Riedl posted to the MOQ working group mailing list on November 20, 2026. -02 of the ad creative signaling draft is posted, this is the one from Thursday's session.... For anyone who missed it, the SCTE-35 Event T…

newsNov 20, 2026via IETF Datatracker

Ad Creative Signaling over the MSF Event Timeline rev 02 lands on the IETF Datatracker

This document defines the carriage of ad creative signaling -- creative identity, tracking events, and measurement verification metadata as specified by SVTA 2053-1 -- in records on a Media over QUIC (MOQT) Streaming Format (MSF) Event Timeline track. It complements the carriage of SCTE-35 splice signaling over the same mechanism: splice events describe where placement opportunities occur on a media timeline, while the event class defined here describes the creatives that fill them and how their playback is to be measured. This binding is the MSF counterpart of the DASH and HLS carriage bindings defined by SVTA 2053-1, which defines none for MOQT.

newsNov 20, 2026via GitHub

New MOQ repo to watch: moqt-rs

Sans-I/O Rust library for Media over QUIC Transport (MOQT) Latest tracked commit 8307e91: 0328 polished 未使用の依存関係を削除し、重複したテストと不要な公開項目を整理する