-
Notifications
You must be signed in to change notification settings - Fork 476
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
SntpClient periodically re-syncs the offset to NTP server #697
Conversation
Many of the Android TV platforms do not report accurate `SystemClock.elapsedRealtime()` In addition this drift is not consistant accross multiple boxes, so the time offset between any pair of boxes will vary over time. This variance will lead to a drift in the Live Offset calculation. Fix is simple, inValidate the NTP server query after a period of time (10 minutes) and re-issue the call
See bug #696 |
@marcbaechinger as you can see, with Google TV time is off by 2 seconds from my workstation (which is a Ventura Mac synchronized to NTP):
With this pull request and the one that fixes #702 we can play video on two devices synchronized. We are shipping this feature on our 1.15 based ExoPlayer product, my company is graciously allowing me to share the required changes. Let me know if you want a live HLS URL to play with I can sent it to a private email only. |
@marcbaechinger do you want me to re-post this based to main? |
Sorry for no hasving responded so far. Yes, please assign to me when done. I'll try to do better then this time. |
No worries @marcbaechinger, we are all busy at our respective day jobs. I'll opened a pull request based to main as well with this same code change, already formatted in Google style. #1794 |
You may as well also approve and merge #1794 since it is the same code already merged to main branch. Or you can simply close pull request. Which ever is easier for you internal git process. |
I'm closing this. Going to proceed with #1794 instead. Thanks Steve! |
Many of the Android TV platforms do not report accurate
SystemClock.elapsedRealtime()
In addition this drift is not consistant accross multiple boxes, so the time offset between any pair of boxes will vary over time.This variance will lead to a drift in the Live Offset calculation.
Fix is simple, inValidate the NTP server query after a period of time (10 minutes) and re-issue the call