Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
playback wrong position
See original GitHub issueHave you read the FAQ and checked for duplicate open issues? Yes
What version of Shaka Player are you using? 2.5.9
Can you reproduce the issue with our latest release version? Yes
Can you reproduce the issue with the latest code from master?
Yes
Are you using the demo app or your own custom app? custom
If custom app, can you reproduce the issue using our demo app? No
What browser and OS are you using? Chrome 80, Windows 10
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs? nodejs simple app with all files: https://drive.google.com/file/d/1TDdqfLEZmpplj6_eZMaQg8F2RPK_5VmP/view?usp=sharing
What did you do?
node index.js
open http://localhost:3000
What did you expect to happen? Playback should start from the beginning.
What actually happened? Total duration is wrong. Start position is wrong.
https://drive.google.com/file/d/1aXquilGNrO6_bXsVyFYjCDyGW0T6hox_/view?usp=sharing
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@One041 That is a known issue: https://github.com/google/shaka-packager/issues/720. Dockerhub auto build stopped working after GitHub authorization update last year. We’ll address it soon. Sorry for the confusion.
Alright, here’s what I see: your manifest is a Live one (mpd type=“dynamic” in the manifest text), so it starts at the live edge, not at the start of the content. This is expected behavior as the manifest tells us to start at that point.
The weird duration thing seems to be a Chrome bug. I can repro this on our demo page using browser native controls. (This is what you’re using on your page as well by specifying ‘controls’ on your video element: <video controls>) I will ping the Chrome team and see if they can take a look. I wonder if this is a bug in how they treat live content.
In the meantime, let’s try and get you going with our custom controls that don’t have the same problem. @joeyparrish can you advise please, they’re including the shaka build from the npm. I changed the link to the ui build: https://cdn.jsdelivr.net/npm/shaka-player@2.5.9/dist/shaka-player.ui.debug.js, but I’m not seeing our CSS. Don’t we bundle it with everything else? Am I missing something? I’m working off the code @One041 provided in the attachment, which seems to be based on our tutorial.