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

Live playback doesn't start - are segments in the future? #1430

Closed
chrisfillmore opened this issue May 2, 2018 · 3 comments
Closed

Live playback doesn't start - are segments in the future? #1430

chrisfillmore opened this issue May 2, 2018 · 3 comments
Labels
status: archived Archived and locked; will not be updated

Comments

@chrisfillmore
Copy link
Contributor

If you guys are willing, I was hoping you could validate my analysis of a problem I'm having with a live stream. I am using Shaka v2.3.4. I am trying to play this manifest:

https://dfwlive-sponsored.secure.footprint.net/Content/DASH.abre/Live/channel(ECTV-2819.dfw.480.mobile)/manifest.mpd

As far as I can tell, the segments are in the future, so playback never starts, and Shaka fetches updated manifests indefinitely.

Using values from my recent testing:

Live edge is:
(current time + clock offset) / 1000 - availabilityStartTime
= ((1525296979574 + (-22925)) / 1000) - 0
= 1525296956.649

First segment start time is:
availabilityStartTime + Period@start + (S@t - presentationTimeOffset) / timescale
= 0 + 1525016546.358 + (193582283794 - 0) / 90000
= 1527167460.6223779

Thus the segments are ~3 weeks in the future.

If this is correct, are there multiple possible paths to resolution? It's not clear to me which value is wrong: Period@start, S@t, PTO...?

I appreciate any insight you can offer. Thanks for the help.

@chrisfillmore
Copy link
Contributor Author

Interestingly, the distance from the live edge appears to be growing. Today segments are ~24 hrs further from the live edge than it was last night.

@chrisfillmore
Copy link
Contributor Author

I now understand that Exo has the behaviour described in #999, and ignores device time in cases of SegmentTemplate + SegmentTimeline.

Our packager restarted the stream last night and it works, but has advised us that it will be a bit unstable as they identify the problems they're having.

Thanks, I will close.

@joeyparrish
Copy link
Member

Okay. Sorry I wasn't able to get to this fast enough to be helpful. We are going to be working toward v2.5 very soon, and #999 is at the top of my agenda for that release.

@joeyparrish joeyparrish removed their assignment May 7, 2018
@shaka-project shaka-project locked and limited conversation to collaborators Jul 3, 2018
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 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
Projects
None yet
Development

No branches or pull requests

3 participants