Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions quest/m1/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -164,6 +164,7 @@ QUIC studies there on that rule.
- [Audio warmup](/quest/m1/audio-warmup.md) - a viewer joining an Opus rendition mid-stream never hears the unconverged first 80 ms
- [#3021](/quest/m1/3021-moq-gst-anchor-generated-media-timelines-to-wall-clock.md) - moq-gst picks the broadcast wall epoch; a restarted source is a new epoch, not a forward re-anchor
- [T-STD TS export](/quest/m1/tstd/README.md) - `moq export ts` is a proper remux that passes the T-STD buffer model, starting with a fixed `--delay`
- [TS passthrough](/quest/m1/ts-passthrough.md) - `--passthrough` carries the multiplex as whole packets, listed in an `m2ts` catalog section, and writes it back byte-identical (less late drops) on a fixed delay
- [FLV export delay](/quest/m1/flv-export-delay.md) - FLV interleaves through the shared fixed-delay release stage
- [MKV export delay](/quest/m1/mkv-export-delay.md) - MKV interleaves through the shared fixed-delay release stage
- [Release profile](/quest/m1/release-profile.md) - every release build gets fat LTO, one codegen unit, and stripping from the workspace profile instead of three script exports
Expand Down
117 changes: 117 additions & 0 deletions quest/m1/ts-passthrough.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,117 @@
# [M] TS passthrough carries the multiplex verbatim on a fixed delay

## Goal

`moq import ts --passthrough` publishes a transport stream without
demultiplexing it, and `moq export ts --passthrough --delay <dur>` writes the
same bytes back out, paced on the source's own PCR and released at a fixed
delay like an SRT receiver. From the first group it releases, the output is
byte-identical to the input, so it is exactly as T-STD-conformant as the
source. It carries what the demultiplexed lane cannot: TS-level scrambling,
private PIDs, and PSI/SI as authored. There is no JS player for it.

## Plan

Decided (2026-10-01), from a discussion with t0ms:

- Why: the [T-STD line](/quest/m1/tstd/README.md) names a passthrough lane as
the only one that can carry primary distribution until the remux passes, and
none exists. Some feeds will want it permanently: the demultiplexed lane
cannot parse a scrambled elementary stream into frames, and an operator
who must hand on SI and private PIDs as authored has nothing to gain from
a remux.
- The track is listed in a new `m2ts` root section of the hang catalog,
not in `video`/`audio` (it has no codec to describe) and not in the
`mpegts` section, whose members (`tracks`, `program`, `si`, ...) record
what demultiplexing loses and are all in-band here. `m2ts` is one object,
`{ track, randomAccess, muxRate }`, naming the broadcast's one passthrough
track. Passthrough always carries the whole multiplex: splitting out a
program would rewrite the PAT, so there is no scope field, and a second
multiplex is a second broadcast. `muxRate` is present only while the
source holds a constant rate, as in `mpegts`. 188-byte packets only; a
192-byte source is refused, so there is no packet-size field. This quest
specifies the section in `drafts/draft-lcurley-moq-mpegts.md` next to
`mpegts`, with its mapping onto MSFTS's track fields. A track is one shape
or the other.
- Objects are runs of whole 188-byte packets on one track. A group starts at
a packet with `random_access_indicator` set on the program's video PID
(its `stream_type` read from the PMT), or on the PCR PID when the program
has no video, so a joiner lands on a decodable picture whichever PID
carries the PCR. A group also starts at any PCR with
`discontinuity_indicator` set, since MSFTS forbids a PCR discontinuity
inside a group. A source that never sets the random-access indicator
falls back to a group every N PCRs (N to be fixed in the PR, with a group
spanning at most 1 s of PCR time). Pacing stays on the PCR PID throughout.
- `randomAccess` is true only while the PAT lists a single program with at
most one video PID, and every group has started at a
`random_access_indicator`. The first group that starts without one (a
fallback, or a `discontinuity_indicator` alone) republishes the catalog
with it false. Any other layout always publishes false, since programs or
video streams sharing a clock can stagger their GOPs.
Both indicators sit in the adaptation field, which TS scrambling leaves in
clear, so a scrambled feed still groups and paces.
- The publisher reads the PAT and PMT (with the existing `ts/psi.rs`
parsers) to find the PCR and video PIDs and count programs, and parses
nothing else past the adaptation field. PSI is never scrambled, and every
byte is still published as received.
- Each object's timestamp is the PCR time of its first byte, interpolated
between PCRs at the stream's own rate, carried in hang's `legacy`
container (a varint timestamp before the packets) as verbatim tracks are.
Object boundaries and timestamps then depend only on the bytes, so two
publishers of one feed publish identical objects, which 1+1 needs.
- A multiplex is paced on one PCR PID: the `PCR_PID` in the PMT of the PAT's
first program, or `--pcr-pid`. Every byte stays in order behind it. Programs
on independent clocks are out of scope.
- The export reuses the [fixed-delay release](/quest/m1/tstd/delay.md)
stage, keyed on each object's PCR time instead of a DTS, which also
spreads each object's bytes at the PCR-implied rate. It must pace on the
source's PCR, not on arrival: a pacer that re-clocks on arrival moves the
PCR-to-PTS offset over a long capture and fails the decoder buffers, even
though every byte is intact.
- An object that misses its deadline is dropped and counted, as the release
stage does. The output shows a continuity error there; passthrough never
rewrites continuity counters.
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Resolved
- Source clock drift is handled by the fixed-delay release's clock recovery
(#4645), shared with the demultiplexed export, not here.
- Passthrough gives 1+1 identity for free: two exporters fed the same
objects emit identical TS packets for every object both release,
continuity counters included, since passthrough never rewrites them; an
object one leg drops late is a gap in that leg only. Aligning the legs in
time is left to the `--sync` anchor planned for the demultiplexed export's
2022-7 legs (`quest/m2/ts-hitless.md`, #4680), which passthrough can adopt.
That is TS identity, not ST 2022-7 recovery, which also needs matching RTP
headers from a coordinated RTP egress.
- Rust only. `js/hang` does not parse `m2ts`, and a player sees no
rendition for the track.
- `--passthrough` publishes only the passthrough track. Publishing it
alongside the demultiplexed tracks is out of scope.

Test: an export of a broadcast capture is byte-identical to the input from the
first released group, and the strict T-STD check gives the same verdict on
output and input. A scrambled fixture (`transport_scrambling_control` set on
its elementary PIDs) groups and paces the same as its clear twin. A
two-program fixture on one clock with staggered GOPs publishes `randomAccess`
false, as does one program with two staggered video PIDs. A single-program
fixture with the PCR on its audio PID starts groups at video random access
points only. PCR discovery finds a PCR PID that differs from the PMT PID, with
the PMT section split across packets. Two exporters fed the same objects with
different arrival skew emit identical bytes; when only one misses a deadline,
its output is the other's less that object's packets. A dropped object is
counted, and the rest still go out on time. Rerun the #4613 netem rig (10%
loss, 120 s) against it.

Update `doc/bin/cli.md` for both flags, `doc/concept` for the section, and
the draft's comparison section to say this repository now publishes both
shapes.

Public API: new import and export modes; nothing existing breaks. Wire: the
hang catalog gains an `m2ts` root section; additive.

## Required

- [Fixed-delay release](/quest/m1/tstd/delay.md) - the release stage this reuses, with its clock recovery (#4645)

## Related

- [MSFTS convergence](/quest/m2/msfts-convergence.md) - the ES-level side of the same mapping
- [TS byte schedule](/quest/m1/tstd/byte-schedule.md) - the remux's equivalent of pacing on the source PCR
4 changes: 4 additions & 0 deletions quest/m1/tstd/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,3 +25,7 @@ nightly.
- [Fixed-delay release](/quest/m1/tstd/delay.md) - frames go out at media time plus a fixed `--delay`, in one order under loss
- [T-STD check](/quest/m1/tstd/check.md) - the harness grades the full buffer model instead of the transport buffer alone
- [TS byte schedule](/quest/m1/tstd/byte-schedule.md) - PCRs sit on the byte grid the mux rate implies, paced against the fixed delay

## Related

- [TS passthrough](/quest/m1/ts-passthrough.md) - the passthrough lane named in the Goal
14 changes: 9 additions & 5 deletions quest/m2/msfts-convergence.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,9 @@

A subscriber author can map this repository's demultiplexed TS lane
(access units, Hang catalog `mpegts` section) onto MSFTS ES-level carriage
without guessing. Transporting TS verbatim is a non-goal.
without guessing. Transporting TS verbatim is out of scope here:
[TS passthrough](/quest/m1/ts-passthrough.md) carries it in an `m2ts`
catalog section that maps onto MSFTS's track fields.

## Plan

Expand All @@ -20,7 +22,9 @@ egress moved to msfts#37 (closed). Two differences remain:
matter to a subscriber, and converge or document the mapping.

Update `drafts/draft-lcurley-moq-mpegts.md` and `doc/concept` with whatever
lands. Open TS PRs [#4577](https://github.com/moq-dev/moq/pull/4577) (per-ES
access units at export), [#4579](https://github.com/moq-dev/moq/pull/4579)
(export on the mux rate), and [#4580](https://github.com/moq-dev/moq/pull/4580)
(per-program SI) touch the same area; land or rebase on them first.
lands. [#4577](https://github.com/moq-dev/moq/pull/4577) (per-ES access
units at export) has merged, and [#4579](https://github.com/moq-dev/moq/pull/4579)
(export on the mux rate) closed in favour of the
[T-STD line](/quest/m1/tstd/README.md).
[#4580](https://github.com/moq-dev/moq/pull/4580) (per-program SI) is still
open and touches the same area; land or rebase on it first.
Loading