-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Stuck in buffering state after the midroll ads finish playing #4681
Comments
I think there may be a combination of two different issues here. The first is that the this ad tag has two empty midroll ad breaks. Handling of those should be fixed on The second is that if I seek past the third midroll we don't seem to get any notification from IMA that the ad break is empty (I see It would help with both issues if you could depend on the development branch, set |
OK. But when I tried dev-v2 Im getting this error: `* What went wrong:
|
Do you have both |
I'm having a similar issue in which if pre-roll is empty and first mid-roll from adgroup is empty it skips the preroll correctly but whenever it gets to the midroll it just gets stuck into a buffering state. Tried with dev-v2 and release-v2 branch with the latest version being 2.8.4 and it didn't seemed to be fixed. |
Also not working for me. |
I've also encountered the issue with the dev-v2 branch and I've set
|
@asolis90, @CipherGit Please could you send the ad tags and full logcat after reproducing the issue with |
I've got a possible fix for these issues (please see the update on #4622) but the ad tag provided via email seems to have only empty ad breaks. Is that expected? Thanks. |
We will send you another ad tag. Because I think the ads already expired on our side. |
If we remove the empty ad break will it work? |
An ad tag without empty ad breaks shouldn't exhibit this issue. |
The previous change was too aggressive as it would clear future ad breaks. Still clear the pending content position so the real content position is reported after an empty ad break. Issue: #4681 Issue: #4622 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=209752306
At the point of starting to play a postroll, source info refreshes for future postroll ads in the same ad group would cause a seek that incorrectly identified the media period to play as the content media period. Fix the logic in getAdGroupIndexForPositionUs to address this. Also handle empty postroll ad breaks by resetting the expected ad group index when we send content complete. Issue: #4710 Issue: #4681 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=210071054
@objectiveCarlo, @asolis90, @CipherGit This should be fixed on the dev-v2 branch. Please could you try it out and let us know if you see any issues? Thanks. |
Right now we don't have the same ad tags anymore cause I think our backend guys did some tweaking. Ill try to get a sample ad tag from them and let you know. Thank you! |
Closing as playback of ad tags with empty ad groups is now working for the various test ad tags I've tried. There is a remaining issue with playback of ad tags where some ads within a non-empty ad group are empty: #5006. |
Issue description
On Android 8.0 and above after the none skippable midroll ads completed playing the player will just buffer
Reproduction steps
Version of ExoPlayer being used
ExoPlayer 2.8.4 and 2.8.1
First observed at 2.8.1
And tried to update at
Device(s) and version(s) of Android being used
Pixel 2 Android 9.0
Samsung Phone Android 8.0
Pixel 2 Android 8.0
This issue is reproducible in the sample app by using the following parameters:
I emailed it to: dev.exoplayer@gmail.com
Thanks
The text was updated successfully, but these errors were encountered: