Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signalling the last segment number in Period #2430

Closed
avelad opened this issue Feb 27, 2020 · 2 comments · Fixed by #6416
Closed

Signalling the last segment number in Period #2430

avelad opened this issue Feb 27, 2020 · 2 comments · Fixed by #6416
Assignees
Labels
component: DASH The issue involves the MPEG DASH manifest format priority: P3 Useful but not urgent status: archived Archived and locked; will not be updated type: enhancement New feature or request
Milestone

Comments

@avelad
Copy link
Member

avelad commented Feb 27, 2020

Add support to the feature described in DASH IOP 4.4.3.6. Signalling the last segment number in Period https://dashif.org/docs/DASH-IF-IOP-v4.3.pdf

As indicated in clause 4.3.2.2, the content provider may not offer the last segment that is signaled in the MPD. If this is the case, the content provider should signal that the last segment is not the one indicated in the MPD.
At least the following three options may be considered:
 - Use the lmsg signalling as defined in clause 4.4.3.5.
 - Use the Segment Timeline with @r value greater or equal to 0.
Add a Supplemental Descriptor with @schemeIdUri set to http://dashif.org/guidelines/last-segment-number with the @value set to the last segment number.

This feature request is add support to <SupplementalProperty schemeIdUri="http://dashif.org/guidelines/last-segment-number" value="368" />

Sample stream: http://dash.akamaized.net/dash264/TestCasesIOP41/LastSegmentNumber/1/manifest_last_segment_num.mpd

@joeyparrish joeyparrish added this to the Backlog milestone Feb 27, 2020
@joeyparrish joeyparrish added the type: enhancement New feature or request label Feb 27, 2020
@joeyparrish
Copy link
Member

Sounds reasonable. Thanks!

@joeyparrish
Copy link
Member

This intersects with my work on #1339, which changes the way we generate segment references for DASH. It will be relatively easy to integrate after that.

@theodab theodab added component: DASH The issue involves the MPEG DASH manifest format priority: P3 Useful but not urgent labels Sep 30, 2021
@avelad avelad self-assigned this Apr 5, 2024
@avelad avelad modified the milestones: Backlog, v5.0 Apr 8, 2024
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Jun 8, 2024
@shaka-project shaka-project locked as resolved and limited conversation to collaborators Jun 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
component: DASH The issue involves the MPEG DASH manifest format priority: P3 Useful but not urgent status: archived Archived and locked; will not be updated type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants