-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frequent DashManifestStaleException errors on Live Dash manifests #1734
Comments
APK and instructions have been sent. I'm available any time to help, thank you! |
I have the same issue when testing a manifest with key rotation. Media3 version 1.3.1 (I have also tried version 1.4.1) The error is either DashManifestStaleException or IndexOutOfBoundsException I already use @tonihei Do you know already if it's an issue on the player's side or if it's something we can fix ourselves? |
I looked into the player code and saw the reasons for the exception to be throwed. media/libraries/exoplayer_dash/src/main/java/androidx/media3/exoplayer/dash/DashMediaSource.java Line 655 in c35a9d6
The issue for us was resolved by adding incremental start times to each new period in the manifest. |
I've been looking at a HAR file from an occurrence. I'm hoping a Media3 dev can help us determine what's going on here. Last period in manifest before the problem is: Suggests Ad break has started and is playing successfully in the player Last two periods in the next manifest are: I believe this is the point that ExoPlayer starts reporting a "buffering" state, and I can see the ..item_init.m4i URLs being loaded that suggests the player is trying to recover from some problem. The period id suggests this next period is of the game (no longer playing Ads). However playback stalls here and we only see the last frame of the Ad Slate. Last five periods in the next manifest are: ExoPlayer is having problems and continues to try to "recover" from some manifest sync issue. It finally gives up with DashManifestStaleException. These three Ad periods (ad-16-2-1, ad-16-3-1, ad-16-4-1) appear in the last manifest (before the Source period) when they were not included in the previous manifest |
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.
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
adb bugreport
to [email protected] after filing this issue.The text was updated successfully, but these errors were encountered: