-
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
Decoder issue while playing MidRoll Ads with Exoplayer 2.14 in Android11 #9358
Comments
Hi Team, |
Thanks for the media & license URL - I don't think you provided an ad tag URL though? So I don't think I can reproduce the exact setup you're seeing. The logcat snippet provided and the behaviour described look like a possible duplicate of #8696 - but I'd like to see some more log output to confirm. I'm specifically looking for lines like this:
If you see those lines logged when you see this problem:
|
HI icbaker, Devices: Error Log:
Thanks, |
Thanks for the ad tag, I can reproduce the problem in the ExoPlayer demo app on a OnePlus AC2003. With With I suspect (haven't debugged in detail) that the reason If you remove the pre-roll the workaround should help. In that case the decoder will be configured for the content, so when the lower-resolution/profile mid-roll ad is played the same decoder can be re-used. This is the same as the situation described in #8696 (comment). |
Duplicate of #8696 |
HI Team,
We are getting below error when tried to play Our DRM Widevine Stream Url with Midroll Ads in Exoplayer 2.14. Player is showing this error when about to play the First Midroll Ad. We are having only Midroll ads. We are using Vmap xml to play Ads. Observed this issue so far only in Android 11 . We tried playing our stream Url with Exoplayer sample app and got same issue .
Due to this issue we were not able to release our app with Ads. Please let us know if any other information is required from us. Please help
As we cannot share the Stream Url and Drm info publicly, we will mail it to dev.exoplayer@gmail.com
Thanks,
The text was updated successfully, but these errors were encountered: