Closed adgllorente closed 4 years ago
Hello @adgllorente ,
Thank you for the detailed information! Would you please provide us your sample manifest url and license info, so that we could verify our fix? You can send an email to shaka-player-issues@google.com . Thanks!
This appears to be caused by our limiting of segment lists for live content. We should avoid limiting segments for VOD. As a workaround, you could increase the limit with manifest.dash.initialSegmentList
configuration (e.g. set to 1e10).
We've removed the streams from our catalog because they were failing.
I'm working to restore the streams, I'll let you know.
Thanks!
The provider of the stream has recoded the stream and fixed the issue so I can't give you an MPD with the issue.
Feel free to close this issue, I'll open another one if it happens again.
Sorry.
Thanks for your time in trying to get the stream back. Sorry we weren't able to help!
Have you read the FAQ and checked for duplicate open issues?
Yes.
What version of Shaka Player are you using? 3.0.1
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? Demo app.
If custom app, can you reproduce the issue using our demo app?
What browser and OS are you using? Chrome.
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
What are the manifest and license server URIs?
I will provide through email a way to get a URL and an issuer license.
Sample Manifest included below:
What did you do? Just start the playback.
What did you expect to happen? Playback should start.
What actually happened? Plaback crashes.
I've seen shaka is replacing the RepresentationId in the Fragment URL (
TK_$Number%08d$.m4f?pbs=c2d47433e3f1485094daa7b6dae25bdd&drm=1&cloud=aws
) with TK0_00001001 but it should use TK0_00000000 when requesting the first fragment, so that, server is returning a 403 code producing a HTTP_BAD_STATUS error.I've been debugging the player and it seems
minPosition
is not properly calculated here https://github.com/google/shaka-player/blame/master/lib/dash/segment_template.js#L347 and it may be related with this commit https://github.com/google/shaka-player/commit/9f448710bc53d5f1ebb6239cacf01f508218e9f2.When replacing that Line with
const minPosition = range[0];
playback works fine but I don't have enough background to know if that's the proper way to fix the bug.I've tested in Dash.JS player and it starts with TK0_00000000 and playback works fine.