Expand description
The channel schedule: an ordered list of entries (programme / ad / slate).
The wire/data format here is deliberately ours to define — issue
#748’s
design-decision comment: SCTE 224 (ESNI) covers policy/blackout
signalling, not channel assembly, and adopting it would be cargo-culting a
standard that does not answer this question. There is no applicable open
standard for “ordered list of sources with planned starts” to transcribe,
so Schedule is a plain in-memory model, not a wire type: it has no
Parse/Serialize pair, and it is deliberately minimal — enough to plan
transitions and the SCTE-35 cues they imply, nothing
about rights, geography, or blackout rules.
Structs§
- Codec
Config Id - Caller-supplied opaque identity for a source’s codec configuration (its
avcC/hvcC/esds, etc.), used only for equality comparison. - Schedule
- An ordered schedule: entries strictly increasing by
planned_start. - Schedule
Entry - One entry in the schedule: a source, its kind, and when it is planned to start on the shared channel timeline.
Enums§
- Entry
Kind - What kind of content a
ScheduleEntrycarries.