-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix support for relative paths in clock sync URIs #376
Comments
|
Your manifest does not contain a In v2.0.0-beta2 we introduced a configuration option for situations where you cannot add Docs: http://shaka-player-demo.appspot.com/docs/api/shakaExtern.html#DashManifestConfiguration
Example: player.configure({
manifest: {
dash: {
clockSyncUri: 'http://foo.bar/time'
}
}
}); The demo app at http://shaka-player-demo.appspot.com/demo/ has a clock sync URI configured, so your manifest should work correctly on that demo regardless of your local clock. (Please let us know if it does not.) Does this answer your question? |
Hi Joe, yes, it did work if i adding your configuration for playing the stream "http://wowzaec2demo.streamlock.net/live/bigbuckbunny/manifest_mpm4sav_mvtime.mpd". but we also developed Dash Stream Server, I found that the live edge of our own stream produced by my server is slow 30 seconds(maybe the system delay from encoder to server) than the time of now, Is there any solutions can be done on player side under these circumstances? Thanks |
Can you clarify what you are asking for? It sounds like you have some bug in your server, but I am not at all sure I understand. |
what i mean is that for example, right now, shaka request the live edge, what it request is the segment which t = 631000 , ( 631000 is the time now 11:10:31 minus the available start time 11:00:00 and unit in millisecond ) the last " and that is my issue, i can not modify anything for the server side. and as i know, shaka v1.3.0 can play these delay live streams. |
The fact that v1.3.0 miscalculated the live edge in a way that compensates for a bug in the server is not a good thing. :-) You should provide <UTCTiming schemeIdUri="urn:mpeg:dash:utc:http-iso:2014" value="/path/to/currentTime"> Where |
Thanks very much, but it seems that i must use an absolute path not the relative path like following code is line 1077 in dash_parser.js: what it requests is the But, if i use the absolute path, there will be another issue, if i want use the CDN to delivery the mpd and content, it will be confused to set the absolute |
Okay, so it seems we need to fix support for relative paths. |
Hi @asdftu, please try again with the latest from |
OK, Thanks very much! |
i checked the code and found that shaka got the playheadtime by calculate "Date.Now - availabilityStartTime - maxSegmentDuration" ,
when my local time is faster or the time of server side is slower, shaka will never found the playback segment.
please help to check,
Thanks
Logan
The text was updated successfully, but these errors were encountered: