-
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
DefaultTimeBar doesn't show the progress #3926
Comments
Please provide complete information as requested in the issue template. The issue template can be found here. |
Hi @erdemguven , I updated the info. Please let me know if I something missed. Also I able to get the length of the video by next way:
|
The given mp4 file header doesn't contain the duration. ExoPlayer relays on the information provided in the header. You might try to re encode the file. |
It's true that the duration is for some reason set to 0 in the sample file (it probably shouldn't be). However it should be possible for us to fill in the missing duration based on the |
It will be great if ExoPlayer will be able to count the duration for files with empty/bad headers. In other case developers need to recreate video file and only then pass to player. |
Issue: #3926 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=188020756
Issue: #3926 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=188020756
Hi, I have purpose to play video from different sources. From network (DASH) I see the progress of seekbar, but when the source is a file - not.
It happened on every time if I try to play from file. I tried different mp4 files.
Seems problem that player can't detect the total length of the video.
How to resolve this issue?
exoplayer v.2.7.0
sony z5, android 7.1.1
any video file can be used, just replace "file_path" with real path.
video for testing: https://www.dropbox.com/s/3y7w8c0e5j1aukt/17900053588159454.mp4?dl=0
code:
On the left side - progress time, on the right - total time.

The text was updated successfully, but these errors were encountered: