cta-wave / dash-hls

For work on the DASH-HLS Interoperability specification
10 stars 0 forks source link

Basic Live Stream #17

Closed technogeek00 closed 3 years ago

technogeek00 commented 4 years ago

Use Case Description

A single in the clear CMAF presentation that is being made available in real time

Working Notes

Open Questions

technogeek00 commented 4 years ago

August 26th Meeting

krasimirkolarov commented 4 years ago

If we would like interop to include Apple devices, the CMAF guidelines should includes the Apple ones (at least the MUST ones).

technogeek00 commented 4 years ago

From experience I would also posit that the common restrictions for segment authoring requirements on Apple devices have become the defacto standard for HLS authored content as well necessitating their inclusions as a form of restriction here.

technogeek00 commented 4 years ago

Properly reading the DASH 4th edition comment clarifies that any excessive duration fluctuation requires SegmentTimeline signalling. Relevant paragraph from 7.2.1 in 4th Edition

In case the @duration attribute is used for the signalling of the duration of Segments, then the MPD start times as defined in subclause 5.3.9.5.3 should provide an approximation of the Media Presentation time TM within the Period. Specifically, the difference between MPD start time and presentation time TP shall not exceed 50% of value of @duration divided by the value of the @timescale attribute. In case the Segment Timeline is used for the signalling of the duration of Segments, then the MPD start times as defined in subclause 5.3.9.5.3 shall provide exactly the Media Presentation time T M within the Period, i.e. the MPD start time is the earliest presentation time of the Segment.

Based on this there are no direct restrictions in DASH or HLS for segment duration or bitrate fluctuation meaning we should omit them from segment authoring guidelines.

We could have an additional note that restrictive device profiles exist with relevant links though if the group feels strongly about this.

technogeek00 commented 4 years ago

9/9 Meeting - Left for implementation by @technogeek00. Information that is relevant for authoring but a non-normative requirement can be detailed as additional informational constraints on the presentation.

technogeek00 commented 4 years ago

Implementation:

Open to review

technogeek00 commented 3 years ago

Implemented in first published document