-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Description
Have you read the FAQ and checked for duplicate open issues?
Yes, however I believe they have been closed based on incorrect assumptions. ( see below )
If the problem is related to FairPlay, have you read the tutorial?
N/A
What version of Shaka Player are you using?
4.16.8
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
Yes
Are you using the demo app or your own custom app?
Demo app
If custom app, can you reproduce the issue using our demo app?
N/A
What browser and OS are you using?
Chrome/Firefox - MacOS
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
N/A
What are the manifest and license server URIs?
We have three manifests that play for 30 minutes each so at any point one of these three should be live.
- https://live.streaming.a2d.tv/asset/20818712.isml/.m3u8
- https://live.streaming.a2d.tv/asset/20818713.isml/.m3u8
- https://live.streaming.a2d.tv/asset/20818714.isml/.m3u8
What configuration are you using? What is the output of player.getNonDefaultConfiguration()?
Same as demo app
What did you do?
- Play one of the provided manifests ( one of them should be live at all times )
- Run
document.querySelector("video").seekable.start(0)in the console
What did you expect to happen?
The value should be 0 as the available segments are static in the manifest, new segments are simply added
What actually happened?
The value changes.
Are you planning to send a PR to fix it?
Nothing planned at the moment, but hopefully.
This has been reported before 2 or 3 times ( that I can find ) and the answer has been that we can use availabilityWindowOverride and that shaka only emulates what is done in Safari.
However while the safari video controls does not allow seeking in live streams the seek range is correct and you can actually seek in that stream ( run document.querySelector("video").seekable.start(0) )