Skip to content

S element changes across updates #50

@technogeek00

Description

@technogeek00

In the timing model 13.6.3 Removing content from the MPD we explicitly make the following restriction on S elements with respect to expired content:

A repeating explicit segment reference (S element with @r != 0) SHALL NOT be removed until all repetitions have expired.

Which, referring back to 9.2.3 Removal of unnecessary segment references, we explicitly allow the following unnecessary references to exist:

The segment reference is defined by an <S> element that uses S@r to define multiple segment references, some of which are necessary.

But what if the service providers pipeline only keeps a fixed amount of segment information available? In this case when a segment falls out of their memory (and subsequently the dvr buffer described by the MPD) they will make the following update to a repeated S element

  • Increment S@t by S@d
  • If S element does not represent the live head as well, decrement S@r by one

As we have defined it this operation is invalid, but the changes made to the MPD are valid and within the other constraints of consistency within the available segment window. Could we relax the referenced restriction to better account for this service provider model?

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions