-
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
ExoPlayer doesn't apply presentationTimeOffset of the DASH EventStream #10460
Comments
The DASH specification doesn't define As a related note, when an Closing this both as "bad media" and as a duplicate of #9969. [*] I looked at |
@ojw28 There are two editions of ISO/IEC 23009-1:2019(E) |
Thanks for the pointer. We will update |
Issue: #10460 #minor-release PiperOrigin-RevId: 463163839
Issue: google/ExoPlayer#10460 #minor-release PiperOrigin-RevId: 463163839
ExoPlayer Version
2.18.0
Devices that reproduce the issue
device independent
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
Expected result
Player changes the playback state to Player.STATE_ENDED at the end of the media
Actual result
Player stays in the playback state Player.STATE_READY
This happens because MetadataRenderer gets stuck right after the start of the playback and can't output pending metadata with pendingMetadataTimestampUs=1657987406382857. This timestamp corresponds to the presentationTime of the Event in the EventStream in the mpd.
When removing EventStream from the mpd or setting presentationTime of the Event to presentationTime - presentationTimeOffset in the mpd, issue disappears.
Media
by email
Bug Report
adb bugreport
to dev.exoplayer@gmail.com after filing this issue.The text was updated successfully, but these errors were encountered: