DASH Support manifest extension using ept/dur information
- Dominant language
- Java
- Stars
- 21.9k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
According to DASH IF IOP4.3 chapter 4.5.3.3 "Extended Segment Information" (https://dashif.org/docs/DASH-IF-IOP-v4.3.pdf) the advanced client should parse the segment to calculate the next segment URL based on the "ept" and "dur" information from the segment boxes and avoid client fetches the MPD. Client only fetch MPD at startup, or when new Adaptation Set is selected, or if Segments or lost, or in case of other operational issues.
I'd like to ask your support for:
1. Is any feature planed to implement this Live optimization in DASH.js?
2.Could you share your expertise on which areas that we can implement this with best alignment to current architecture, which potentially feedback as pull-request?
BTW, the method in DashMediaSource::processManifest has hardcoded " minUpdatePeriodMs = 5000;" when minUpdatePeriodMs is 0 from manifest. The comment there shows there is improvement planed.
Thanks a lot for your support!
jzhou
Contributor guide
Assessment
This issue has not been assessed yet.