diff --git a/quest/m1/README.md b/quest/m1/README.md index db14564f346..6cd7360f8f8 100644 --- a/quest/m1/README.md +++ b/quest/m1/README.md @@ -172,6 +172,7 @@ removed). - [moqsrc max-delay](/quest/m1/gst-max-delay.md) - GStreamer's `moqsrc` takes a `max-delay` property instead of a hard-coded 1 s budget - [JS join tests cover draft 20](/quest/m1/join-tests-draft20.md) - join.test.ts runs on every supported draft, not just 18 and 22 - [Poll-first async](/quest/m1/poll-first/README.md) - library crates compile no coroutines by default: async wrappers are generated from `poll_*` and gated behind an `async` feature +- [Audit retention defaults](/quest/m1/max-age-defaults.md) - every max-age default listed, with a proposed finite default for the maintainer - [Binding announcements always carry captures](/quest/m1/ffi-required-captures.md) - moq-ffi and its generated bindings make `captures` a required list, as #7266 always sets it - [HLS export follows a resolution change](/quest/m1/hls-reinit-same-codec.md) - a decoder-identity change under the same codec string starts a new init and segment tag - [A JS reader finishes after a clean close](/quest/m1/js-close-range-finish.md) - a range ending below the cache delivers what's held and then ends diff --git a/quest/m1/max-age-defaults.md b/quest/m1/max-age-defaults.md new file mode 100644 index 00000000000..52fcb3a82b8 --- /dev/null +++ b/quest/m1/max-age-defaults.md @@ -0,0 +1,15 @@ +# [S] Audit retention defaults and propose a finite max-age + +## Goal + +Every max-age and cache-retention default in Rust, JS, and FFI is listed with where it applies (producers, relay cache, the IETF absent-MAX_AGE meaning), and the maintainer has a concrete proposal for a finite default to decide on, so no retention is unlimited by accident. + +## Plan + +Decided 2026-10-30 (maintainer): asked whether max-age should default to 0 instead of infinite, like max_delay, which [moq-dev/moq#7403](https://github.com/moq-dev/moq/pull/7403) settled (JS and Rust default 0; unlimited is explicit `None`/`null`). For max-age, audit first and propose. + +- Inventory each default with path:line: `track::Producer`/catalog/media producers, the relay cache's eviction and pool, JS `maxAge` (omitted means no publisher limit in `@moq/net`'s `Info`, while `@moq/hang`'s `trackInfo` substitutes 30 s, matching `hang::container::MAX_AGE`), FFI, and the IETF publisher treating an absent MAX_AGE as unlimited (wire semantics; likely kept). +- Say what 0 would break: late joiners, fetch of a non-latest group, DVR/archive. +- Propose a default with its reason and the migration; the maintainer decides, then a follow-up implements it. + +Public API: none in this quest. Wire: none. diff --git a/quest/m2/README.md b/quest/m2/README.md index bf02f99b38f..27219db595d 100644 --- a/quest/m2/README.md +++ b/quest/m2/README.md @@ -109,7 +109,7 @@ lite-07; bitrate enforcement is not part of this release. - [Resume as producer replacement](/quest/m2/resume-redesign.md) - route changes replace the writer of one track state, deleting the per-reader resume path in Rust and JS - [moq-transport requests end through one lease](/quest/m2/ietf-request-lease.md) - every IETF request ends through one polled lease, and the two 18k-line files split by mechanism - [A moq-transport group head fills its hole in place](/quest/m2/ietf-fill-refill.md) - fills and joining FETCHes write into the tail's group, deleting the `Fill` handoff -- [moq-transport hole markers](/quest/m2/ietf-hole-marker.md) - a negotiated extension names a SUBSCRIBE's holes, so our publishers answer multi-group FETCH from caches that know every group +- [moq-transport hole markers](/quest/m2/ietf-hole-marker.md) - a negotiated extension names a SUBSCRIBE's holes, so our publishers answer multi-group FETCH from caches that know every group; built when an IETF client wants it - [Announce interest streams share one route table](/quest/m2/announce-interest-memory.md) - per-stream announce cost follows what is in flight, not every route - [One relay serve path for every runtime](/quest/m2/relay-serve-path.md) - io_uring serves through the shared `Connection::serve` and config mapping - [A parked read of a resumed group reads its budget without re-syncing](/quest/m2/recover-budget.md) - measure, then drop the per-frame reader sync @@ -232,6 +232,7 @@ lite-07; bitrate enforcement is not part of this release. - [moq-gst playback shares one session context](/quest/m2/gst-session-context.md) - the playback helpers take one context instead of six arguments - [moq-bench pins the instances it measures](/quest/m2/bench-epoch-pin.md) - pooled requests pin their announced epoch, so a takeover is not counted as the same broadcast - [Bindings see a broadcast end](/quest/m2/binding-broadcast-end.md) - `MoqBroadcastConsumer` exposes the close, and a moq-transport run end is a protocol error +- [Audio track changes are gapless](/quest/m2/gapless-audio-switch.md) - no silence beyond a frame on audio format or rendition changes, enforced by media QA - [We own our WebRTC stack](/quest/m2/webrtc/README.md) - moq-rtc becomes moq-webrtc with moq-ice, the data-channel transport, and a vendored, trimmed str0m/dimpl/is/sctp-proto - [Certificate reload and qmux's tasks are supervised](/quest/m2/tls-reload-supervision.md) - a panic in either fails loudly instead of silently stopping - [PUBLISH_DONE says why](/quest/m2/publish-done-codes.md) - GOING_AWAY, TOO_FAR_BEHIND, and EXPIRED round-trip as stream codes diff --git a/quest/m2/gapless-audio-switch.md b/quest/m2/gapless-audio-switch.md new file mode 100644 index 00000000000..4b36e85558a --- /dev/null +++ b/quest/m2/gapless-audio-switch.md @@ -0,0 +1,15 @@ +# [M] Audio track changes are gapless + +## Goal + +When a browser publisher changes audio sample rate or channel count, or a player switches audio renditions, playback has no silence beyond one decoder frame, and `just test media` fails when the longest gap exceeds that. + +## Plan + +Decided 2026-10-30 (maintainer, from [moq-dev/moq#7374](https://github.com/moq-dev/moq/pull/7374)): land the media QA cases with the gap reported, then fix the gap here. Today's longest gaps: 250 ms on a sample-rate change, 250–300 ms on a channel change, 50–70 ms switching to a second rendition, 200–280 ms switching back, and 200 ms native Opus to AAC. On the sample-rate change the publisher briefly drops audio from its catalog. + +- Publisher: keep the old audio track listed until the new one has its first group, so the catalog never goes without audio. +- Player: start decoding the new track before stopping the old one, and switch at a frame boundary. +- Turn #7374's `longest audio gap` report into a failing check with a one-frame bound. + +Public API: none expected. Wire: none. diff --git a/quest/m2/ietf-hole-marker.md b/quest/m2/ietf-hole-marker.md index a6e3c74328f..32267578599 100644 --- a/quest/m2/ietf-hole-marker.md +++ b/quest/m2/ietf-hole-marker.md @@ -19,6 +19,10 @@ other range stays refused, as [moq-dev/moq#7204](https://github.com/moq-dev/moq/pull/7204) leaves it. +A live ordered reader on an extension-carrying SUBSCRIBE stops waiting at a +signalled hole, as it already does on moq-lite with SUBSCRIBE_DROP. Peers +without the extension behave as today. + ## Plan Decided with the maintainer on 2026-10-28 (`/quest-plan`, "what's not worth @@ -33,6 +37,19 @@ Decision prompts: - Scope: ✅ extension plus range FETCH from caches that know every hole, in m2; extension only; both in m1. +Decided 2026-10-30 (maintainer, from +[moq-dev/moq#7403](https://github.com/moq-dev/moq/pull/7403)), on detecting +unsignalled holes on a live moq-transport SUBSCRIBE: + +- Unsignalled holes are a moq-transport protocol bug. Until a peer signals + them, an ordered reader with an unlimited budget blocks at an owed hole on + a moq-transport SUBSCRIBE. That's accepted, and documented on + `Ordered`/`max_delay`. +- No FETCH to learn whether a hole will fill: it races the live + subscription. No inference from later groups, and no grace periods. +- Build this extension when an IETF client wants it; until then this quest + waits on that demand. + Only peers that implement the extension benefit, which today means our own Rust and JS moq-transport stacks. Our own peers talk moq-lite to each other, so the payoff is third-party adoption. Write the draft so it can be proposed @@ -61,3 +78,7 @@ Our publishers answer multi-group FETCH and fills over known caches. ## Required - [Drop set](/quest/m1/drop-set.md) - the per-track runs that say which groups are known holes + +## Related + +- [Ordered reads wait only on owed groups](https://github.com/moq-dev/moq/pull/7403) - the ordered-reader wait a signalled hole ends