For DASH manifests, we merge min/max live latency values from various sources and they may not be consistent with each other. To ensure we use a sensible configuration in all cases, we can add more correctness checks: 1. Limit the min/max values to fall into the available live window. 2. Ensure that maxLatency >= minLatency in all cases. Issue: google/ExoPlayer#9750 PiperOrigin-RevId: 415282938
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| manifest | Loading commit data... | |
| offline | Loading commit data... | |
| BaseUrlExclusionList.java | Loading commit data... | |
| DashChunkSource.java | Loading commit data... | |
| DashManifestStaleException.java | Loading commit data... | |
| DashMediaPeriod.java | Loading commit data... | |
| DashMediaSource.java | Loading commit data... | |
| DashSegmentIndex.java | Loading commit data... | |
| DashUtil.java | Loading commit data... | |
| DashWrappingSegmentIndex.java | Loading commit data... | |
| DefaultDashChunkSource.java | Loading commit data... | |
| EventSampleStream.java | Loading commit data... | |
| PlayerEmsgHandler.java | Loading commit data... | |
| package-info.java | Loading commit data... |