Frequent DashManifestStaleException errors on Live Dash manifests
@tonihei is already working on this.
Since Sep 17, 2024.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 955
- Avg merge
- 12d 14h
- Merged PRs (30d)
- 2
Description
Version
Media3 1.4.1
More version details
This has been observed on Media3 1.2.1+ (may exist on previous versions as well)
Devices that reproduce the issue
Not device specific, occurs on a variety of devices and versions
Devices that do not reproduce the issue
None known
Reproducible in the demo app?
Not tested
Reproduction steps
Our professional sports and other live content is DRMed, thus we cannot attempt to reproduce this in the Demo app. We will send an email with a debuggable APK with EventLogger turned on and instructions on how to log in/find content.
- Play Live Dash stream with SSAI injection(this includes most of our Live content)
- Allow the stream to play uninterrupted for a period of time
- Observe periodic DashManifestStaleException errors (this comes from the "Loaded out of sync manifest" case in
DashMediaSource.java)
We understand that our Live streams may have an issue we need to try to fix for Media3, but there are other players (such as Roku) which do not have this frequent problem playing the same Dash streams. We are hoping to identify the issue and get a Media3 fix or have our Video provider help us adjust the manifests/SSAI periods.
Note that I have also opened the following Issue that has an easy-to-recreate "indefinite buffering" issue that is related to our SSAI ad-break periods, where as this DashManifestStaleException error is periodic/random. I'm hoping the two are related and we can squash both at the same time, but that one may be worth looking at first.
Live DASH Manifest indefinite buffering occurs between SSAI ad period and content #1636
Expected result
No DashManifestStaleException
Actual result
Frequent DashManifestStale exceptions (maybe every 20-30 minutes)
Media
Sending an email with a debuggable APK, user credentials, recreation details.
Bug Report
- You will email the zip file produced by
adb bugreportto android-media-github@google.com after filing this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.