-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
DASH live stream broken with presentationTimeOffset #143
Comments
Looks like its the issue with time. its either trying to play from the past or from future. Can someone help me identifying this. |
What does this actually says @availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 3876.003000020981 latestAvailableSegmentEndTime 16023.052288888888 Is the player trying to play the segments which is not generated yet? or the ones which were too old? |
Thanks for the report we'll take a look. |
I believe there may be an issue with how the player handles the
|
@randeeppr We are still waiting for your feedback on this.
|
Hi Joey, Thank you. |
We have found that we do, in fact, have a bug in Shaka Player around our handling of presentationTimeOffset, specifically for live streams. I've updated the tags and title to reflect this, and I'm reopening the issue until we can publish a fix. |
Hi,
We are trying to play a unencrypted dash live stream from envivio encoder but we are getting assertion failed errors.
mpd is as follows.
And we are getting the following error on the shaka player.
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 765.0079998970032 latestAvailableSegmentEndTime 5179.632011111111
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 765.0079998970032 latestAvailableSegmentEndTime 5179.573188888889
Starting each stream from 5164.593189108234
Timestamp correction -5119.493188111111
Assertion failed:
video.currentTime (45.100000888889554) should be within the stream limits {"start":5119.94301121983,"end":5119.94301121983}
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 766.0079998970032 latestAvailableSegmentEndTime 5179.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 766.0079998970032 latestAvailableSegmentEndTime 5179.632011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Player error CustomEvent {detail: Error: The browser failed to decode the media content.
at shaka.player.Player.onError_ (http://1…, srcElement: null, target: s…a.p…r.Player, currentTarget: s…a.p…r.Player}bubbles: truecancelBubble: falsecancelable: falsecurrentTarget: shaka.player.PlayerdefaultPrevented: falsedetail: Error: The browser failed to decode the media content.
at shaka.player.Player.onError_ (http://172.16.0.6/shaka-player-master/lib/player/player.js:403:15)eventPhase: 0path: Array[0]returnValue: truesrcElement: nulltarget: shaka.player.PlayertimeStamp: 1438440908170type: "error"proto: CustomEvent
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 776.0039999485016 latestAvailableSegmentEndTime 5189.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 776.0039999485016 latestAvailableSegmentEndTime 5189.616011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 786.0039999485016 latestAvailableSegmentEndTime 5199.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 786.0039999485016 latestAvailableSegmentEndTime 5199.600011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 796.0039999485016 latestAvailableSegmentEndTime 5209.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 796.0039999485016 latestAvailableSegmentEndTime 5209.584011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 806.0039999485016 latestAvailableSegmentEndTime 5219.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 806.0039999485016 latestAvailableSegmentEndTime 5219.632011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 816.0079998970032 latestAvailableSegmentEndTime 5229.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 816.0079998970032 latestAvailableSegmentEndTime 5229.616011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 826.0039999485016 latestAvailableSegmentEndTime 5239.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 826.0039999485016 latestAvailableSegmentEndTime 5239.600011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 836.0090000629425 latestAvailableSegmentEndTime 5249.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 836.0090000629425 latestAvailableSegmentEndTime 5249.584011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 846.0039999485016 latestAvailableSegmentEndTime 5259.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 846.0039999485016 latestAvailableSegmentEndTime 5259.632011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 856.0039999485016 latestAvailableSegmentEndTime 5269.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 856.0039999485016 latestAvailableSegmentEndTime 5269.616011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 866 latestAvailableSegmentEndTime 5279.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 866 latestAvailableSegmentEndTime 5279.600011111111
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
Manifest updated!
Assertion failed:
Http headers are given below.
curl -I http://172.16.0.11/dash/test1/manifest.mpd
HTTP/1.1 200 OK
Content-Length: 0
Server: Halo Origin Server
Content-Type: text/xml
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Origin,Content-Type,Access-Control-Allow-Origin,Range,Accept
Access-Control-Expose-Headers: Access-Control-Allow-Origin, Content-Length, Content-Type, Date, Range, Server, Transfer-Encoding
Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
Date: Sat, 01 Aug 2015 15:37:07 GMT
Connection: keep-alive
Do we need to change anything?
Regards,
Randeep
The text was updated successfully, but these errors were encountered: