-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
HLS - support manifest with several #EXT-X-MAP tags #2397
Comments
This isn't about having multiple |
Hello @ppatlolla-turner , I tested with your sample file, however it looks like it doesn't have multiple EXT-X-MAP tags, and I didn't see any error message. Could you please send us another file that has multiple EXT-X-MAP tags? Thanks! |
Are you testing HLS version or DASH version? DASH should work fine. |
Got it. Thanks! |
This will be fixed as part of our discontinuity work. |
Hello @ppatlolla-turner , This code change is on our latest nightly build https://nightly-dot-shaka-player-demo.appspot.com/ . |
Hi @michellezhuogg Just emailed the url's in a text file. Please try and confirm. If it still doesn't work I need to check if geo-location is turned on. Are you checking form outside US? |
Sorry I was too fast. Stream wouldn't continue playing after the first program segment. |
Thank you! Verified that the video can play until 3:25, keeps buffering for more than 5 secs before it continues to play. Similar for earlier playback. |
Yes it continues it play after 3:25 but only after a long period off buffering. |
Have you read the FAQ and checked for duplicate open issues?
Yes
Is your feature request related to a problem? Please describe.
All our content has program segments and each program segment starts with a different init file. One of the primary reason to have multiple EXT-X-MAP tags.
Describe the solution you'd like
Describe alternatives you've considered
Dash version does work but won't be able to use dash manifest in our workflows.
Additional context
Will send sample streams with multiple #EXT-X-MAP tags via email.
The text was updated successfully, but these errors were encountered: