-
Notifications
You must be signed in to change notification settings - Fork 484
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
Not able to play HLS stream - Loading finished before preparation is complete #2141
Comments
Hi @grbaczek, By trying to play both the two provided urls on demo app, I found that for that "not working" stream, there is never a According to the HLS spec - "Each Transport Stream Segment MUST contain a PAT and a PMT, or have an EXT-X-MAP tag (Section 4.3.2.5) applied to it. The first two Transport Stream packets in a Segment without an EXT-X-MAP tag SHOULD be a PAT and a PMT." Could you please make sure that the TS segments in the stream follow the spec? |
Hi @tianyif thx for you answer - I will look into it |
I have run part_0000.ts (not working):
part_0000.ts (working):
Streams are generated with the command (ffmpeg 6.1.2-r1):
|
Ok, I can actually see there is sth off here |
Version
Media3 main branch
More version details
https://github.com/androidx/media.git - Commit hash: 76088cd
Devices that reproduce the issue
Android emulator API - 33, 34, 35
Devices that do not reproduce the issue
Haven't found any
Reproducible in the demo app?
Yes
Reproduction steps
Add HLS stream to demo app media.exolist.json file
Expected result
I expect stream to play
Actual result
Player seems to be loading all the files one by one - it fails after loading all the files with
androidx.media3.common.ParserException: Loading finished before preparation is complete. {contentIsMalformed=true, dataType=1}
Stream works as expected on iOS and VLC player (Version 3.0.20 Vetinari (Apple Silicon))
Note that all hls media files calls redirect (303) to CDN. This has been working as expected for most of the streams.
Media
I am sending link to the stream on [email protected]
Bug Report
adb bugreport
to [email protected] after filing this issue.The text was updated successfully, but these errors were encountered: