search

Dash-Industry-Forum / Guidelines-TimingModel

DASH-IF implementation guidelines: the DASH timing model
9 stars 1 forks source link

Availability during EarilestRemovalPoint #23

Closed irajs closed 4 years ago

irajs commented 5 years ago

"Let EarliestRemovalPoint be AvailabilityWindowEnd + MPD@minimumUpdatePeriod. Media segments that overlap or end before EarliestRemovalPoint might be considered by clients to be available at the time the MPD update is processed."

the segments after AWE are not available but their addresses are fixed and won't change. So change it to:

Let EarliestRemovalPoint be AvailabilityWindowEnd + MPD@minimumUpdatePeriod. The references to Media segments that overlap or end before EarliestRemovalPoint can be considered by clients to be valid at the time the MPD update is processed. Note that he segments with start point after AvailabilityWindowEnd might not be available at the time of MPD update."

sandersaares commented 5 years ago

I do not understand the comment and the proposed change. Please clarify what you mean.

The text in question received some updates today - maybe the new wording is already more clear? Please revisit the chapter in question and see if whatever the issue is remains.

sandersaares commented 5 years ago

@irajs did you manage to take another look?

sandersaares commented 5 years ago

@irajs if you have a moment, please check if the issue got resolved.

It looks good to me so I think unless there is further comments this issue can be closed.

sandersaares commented 4 years ago

No further comments, so I assume all is well. Regardless, the text has undergone improvement meanwhile anyway.