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

**3.0.X** dash multiperiod timeline playback failure, **2.5.19** works, dashif **3.2.0** works #3139

Closed
arturpilaszkiewicz opened this issue Feb 5, 2021 · 7 comments
Assignees
Labels
status: archived Archived and locked; will not be updated type: bug Something isn't working correctly
Milestone

Comments

@arturpilaszkiewicz
Copy link

Hi,
I've got a problem regarding stream playback of dash timeline with multiperiod change every ~60s

shaka 3.0.X (3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, 3.0.6, 3.0.7)
https://shaka-player-demo.appspot.com/demo/#audiolang=en-GB;textlang=en-GB;uilang=en-GB;asset=//r.dcs.dev.redlabs.pl/livedash/o2/ATM-Lab/zos/usr/ap/07.livx;panel=CUSTOM%20CONTENT;build=uncompiled

  • plays a bit of content
  • goes into spinner
  • fragments new fragments are not acquired, the buffer is emptied
  • plays a bit of content
  • and so on
  • player reports
Jumping forward 11.226612210273743 seconds to catch up with the seek range
  • playback failure is within ~20s of stream playback

shaka 2.5.19
https://v2-5-19-dot-shaka-player-demo.appspot.com/demo/#audiolang=en-GB;textlang=en-GB;uilang=en-GB;asset=https://r.dcs.dev.redlabs.pl/livedash/o2/ATM-Lab/zos/usr/ap/07.livx;panel=CUSTOM%20CONTENT;build=uncompiled

  • maintains buffer
  • no problems with playback

dashif 3.2.0
https://reference.dashif.org/dash.js/v3.2.0/samples/dash-if-reference-player/index.html

  • no problem

Could you please help me why this might be happening ?
I cannot see nothing out of ordinary in changelogs, that could impact playback.
How should I proceed to debug this playback issue ?

@arturpilaszkiewicz arturpilaszkiewicz added the type: question A question from the community label Feb 5, 2021
@TheModMaker
Copy link
Contributor

Next time please use the bug template for this kind of issue. It looks like when playing, we cannot find the segment reference we need. There is some problem with the segment index.

@TheModMaker TheModMaker added type: bug Something isn't working correctly and removed type: question A question from the community labels Feb 22, 2021
@TheModMaker TheModMaker added this to the v3.1 milestone Feb 22, 2021
@arturpilaszkiewicz
Copy link
Author

Ok thanks, does it mean that we are producing an improper manifest ?

@TheModMaker
Copy link
Contributor

Probably not. I'm referring to our segment index that we create from the manifest. This is probably a bug on our part.

@ismena
Copy link
Contributor

ismena commented Apr 2, 2021

Hi @apilaszkiewicz
Seems like the content is no longer available. Could you please verify/update the manifest? Thanks!

@arturpilaszkiewicz
Copy link
Author

@ismena its back online, we had ~3 hours of downtime due to server error.

@ismena
Copy link
Contributor

ismena commented Apr 2, 2021

Look how lucky I am! :)

I found the root cause and am considering the best way to address it. I should have a fix for this next week.

@ismena
Copy link
Contributor

ismena commented Apr 12, 2021

Update: the fix is in review. It's failing some tests now, so it might be a few days until it's merged, but it's 100% on track for v3.1 release.

joeyparrish pushed a commit that referenced this issue Apr 22, 2021
In live streams, we can evict segments outside the availability window
faster than they disappear from the manifest. If that happens, we used
to evict them several times (add them back in and then evict again).
This caused the eviction counter to increase beyond what it should be
and we had trouble finding segments afterwards.

Closes #3139
Closes #3169

Change-Id: Iafebfaf8e1e9ebb09a64cdf7e09a882115fd8eb6
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Jun 13, 2021
@shaka-project shaka-project locked and limited conversation to collaborators Jun 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: archived Archived and locked; will not be updated type: bug Something isn't working correctly
Projects
None yet
Development

No branches or pull requests

4 participants