Skip to content
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

Reference Player with LL Mode is not playing on the live edge #3144

Closed
5 tasks done
huseyinunified opened this issue Dec 20, 2019 · 8 comments
Closed
5 tasks done

Reference Player with LL Mode is not playing on the live edge #3144

huseyinunified opened this issue Dec 20, 2019 · 8 comments

Comments

@huseyinunified
Copy link

@huseyinunified huseyinunified commented Dec 20, 2019

====================

Line:Col[14:31]:cvc-complex-type.2.4.a: Invalid content was found starting with element 'ServiceDescription'. One of '{"urn:mpeg💨schema:mpd:2011":ProgramInformation, "urn:mpeg💨schema:mpd:2011":BaseURL, "urn:mpeg💨schema:mpd:2011":Location, "urn:mpeg💨schema:mpd:2011":Period}' is expected.

MPD validation not successful - DASH is not valid!

Steps to reproduce
  1. Use the Reference Player version 3.0.0 and enable Low Latency Mode from the options.
  2. Use the Reference Player version 3.0.1, no need to change the default settings.
  3. Load the manifest file
Observed behaviour
  1. When LL Mode is enabled stream does not start from the live edge. It goes an earlier point of the archive. But if you remove the LL Mode Option and load the manifest again, it starts playing from the live edge.
  2. The stream has ServiceDescription which works with LL Mode without need the LL Mode option is checked. So behavior is the same, it starts playing some point in the past. But there is no chance to take it back like 3.0.0. So 3.0.1 never starts playing on the live edge.
@thehusmin
Copy link

@thehusmin thehusmin commented Apr 15, 2020

Hi,

Could you please provide an update about the status and why it is unassigned?

Thanks!

@dsilhavy
Copy link
Collaborator

@dsilhavy dsilhavy commented Apr 15, 2020

Hi @thehusmin ,
the developer who was looking into this is not longer working on dash.js. We will try to look into it in one of the next sprints.

@dsilhavy dsilhavy added this to the 3.1.1 milestone Apr 15, 2020
@dsilhavy dsilhavy self-assigned this Apr 15, 2020
@dsilhavy
Copy link
Collaborator

@dsilhavy dsilhavy commented Apr 16, 2020

@thehusmin : In your MPD the @minBufferTime is set to 10seconds while the target latency is set to 2seconds and your minimum latency is 1second. I think @minBufferTime should be equal or less than your minimum latency.

@dsilhavy
Copy link
Collaborator

@dsilhavy dsilhavy commented Apr 16, 2020

@thehusmin I made some changes to the segment request logic, can you please check against the latest nightly build: https://reference.dashif.org/dash.js/nightly/samples/dash-if-reference-player/index.html

@thehusmin
Copy link

@thehusmin thehusmin commented Apr 20, 2020

Hi @dsilhavy, I've checked the stream and start time looks correct.

But the stream does not play as expected that it's having glitches. I tested the same stream with version 3.0.3 and it plays without glitches.

@dsilhavy
Copy link
Collaborator

@dsilhavy dsilhavy commented Apr 20, 2020

@thehusmin In my tests the glitches are caused by the target latency. The maximum latency is set to 6sec which seems to result in frequent buffer underruns. 3.0.3 plays 300seconds behind live edge, so the buffer is never empty.

@dsilhavy
Copy link
Collaborator

@dsilhavy dsilhavy commented May 4, 2020

@thehusmin Do you confirm that the changes in the nightly player fix the problem? As described before, low latency playback results in small buffer and potential buffer underruns.

@dsilhavy
Copy link
Collaborator

@dsilhavy dsilhavy commented May 12, 2020

Problem with starttime has been fixed in #3217

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants