Sync System Clock with SageTV Server - accurate?

[Denali]

Originally Posted by tvmaster2

and and... under "Configure", why do you use a negative offset as opposed to a positive one, and do you disable or enable "Local Server"?

Dish Network tends to be slow on program start times. Reading the documentation for Atomic TimeSync should answer your last question.

[tvmaster2]

Originally Posted by Denali

Dish Network tends to be slow on program start times. Reading the documentation for Atomic TimeSync should answer your last question.

thanks. I read it, and it didn't completely make sense to me.

[reggie14]

This is obviously overkill, but I use the Windows NTP client found here. It includes a Windows service option.

The native Windows time sync client ought to be good enough, but despite hours of playing around with registry settings I could never get it to reliably sync more than once per week. Sometimes I could get it to report it was syncing more regularly, but after looking at my event logs I'm pretty sure the time/date GUI was lying.

[Denali]

Originally Posted by tvmaster2

thanks. I read it, and it didn't completely make sense to me.

If you have other computers on your network, they can sync to Atomic TimeSync.

[peternm22]

Has anyone else noticed their clocks drifting about 23 seconds fast the last week? I think the EPG server might be running fast.

I made sure to sync my time with the above posted application. I then ran an EPG update, and my clock jumped 23 seconds ahead.

Just me or is anyone else seeing this?

[Denali]

Did you disable Windows Date and Time Internet sync? Otherwise if your using an offset in Atomic TimeSync it would be overridden. I don't sync to SageTV Server.

[peternm22]

The internal Windows time sync works fine on my system. Forcing a sync with it produces a correct time (the same time as the atomic time sync app).

The only clock that seems off is the SageTV EPG server.