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

Seek takes a long time if representation changes #191

Closed
dg-vewd opened this issue Jan 22, 2021 · 6 comments
Closed

Seek takes a long time if representation changes #191

dg-vewd opened this issue Jan 22, 2021 · 6 comments

Comments

@dg-vewd
Copy link

dg-vewd commented Jan 22, 2021

Environment

Browser: Google Chrome 87
Bigscreen Player: 4.6.0
Stream: default

Reproduction

Use stream with multiple representations. Continue seeking until seek takes noticeably long time ~5-10 seconds.

This is also observed in iPlayer and CATAL. The order of events that triggers this issue might be a little hard to achieve. It's much easier to reproduce with bandwidth throttling.

The issue

This is the order of events leading to the issue:

  1. Seek to time t
  2. Fragment with id i for time t is requested and download started
  3. Before download is finished, there is drop in measured bandwidth and representation changes
  4. The request for id i is abandoned (because of quality change)

After this, next download request is for fragment with id i+1. New segments are downloaded and this continues for some time. Seek is ongoing because the fragment with time t is missing. Please see buffer ranges in attached log. It might take 5-10 seconds until the right fragment is requested again and playback finally starts.

This is the bug in dash.js and does not reproduce on dash reference player in version 3.2.1. Bigscreen Player is using older version of dash.js. From what I was able to find, changes that seem to fix the issue are introduced in version 3.1.2. This one in particular: #3308. Could you look into this?

Logs

longseek.log

@Luke-Chatburn
Copy link
Contributor

@dg-vewd Thanks for providing such detailed information. As a team we are trying to come up with a solution that allows us to keep bigscreen-player more inline with the main dash.js.

@dg-vewd
Copy link
Author

dg-vewd commented Jan 28, 2021

That's great! Let me know if you have any updates.

@dg-vewd
Copy link
Author

dg-vewd commented Feb 4, 2021

Hello @Luke-Chatburn, are you be able to tell us when the issue could be handled, even a rough estimation would be helpful.

@Luke-Chatburn
Copy link
Contributor

@dg-vewd Sorry, this should be picked up soon. If I get a more accurate time scale I will try and update here.

@domjacks
Copy link
Contributor

@dg-vewd Hi. We've now released an updated version of bigscreen-player along with Dash.js v3.2.0.

Let me know if this resolved your issues 😄

@dg-vewd
Copy link
Author

dg-vewd commented Jun 1, 2021

Hi! I can no longer reproduce this issue with new version of bigscreen-player. Thanks a lot 😃

@dg-vewd dg-vewd closed this as completed Jun 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants