All recordings start 2 min late

[wvpolekat]

I recently updated my Sage server to a spiffy new dual core 3.0 ghz machine. I did the whole backup/restore thing and moved all my recordings over and it worked perfect.

The only problem I am still having is that all recordings start and end exactly 2 min late.

It is not a delayed channel change where it starts recording and then the channel changes (USB-UIRT), I have seen those before.

In this case, the recording doesn't start until X:02 or X:32 and the OSD on the cable box indicates that.

I have checked that there is 0 default padding before and after. Checked the system clock and it is dead on and agrees with the cable box.

I tried adding 2 min padding to/from either end and it did not change it.
Set it to sync with the sage time source, no change.

Any ideas would be welcome!

[stevech]

Originally Posted by wvpolekat

I recently updated my Sage server to a spiffy new dual core 3.0 ghz machine. I did the whole backup/restore thing and moved all my recordings over and it worked perfect.

The only problem I am still having is that all recordings start and end exactly 2 min late.

It is not a delayed channel change where it starts recording and then the channel changes (USB-UIRT), I have seen those before.

In this case, the recording doesn't start until X:02 or X:32 and the OSD on the cable box indicates that.

I have checked that there is 0 default padding before and after. Checked the system clock and it is dead on and agrees with the cable box.

I tried adding 2 min padding to/from either end and it did not change it.
Set it to sync with the sage time source, no change.

Any ideas would be welcome!

Dare I ask the obvious?
Is the clock in the PC and the cable box the same as NIST? The broadcaster's use that. WIndows XP clock has an option to synch with NIST. I use us.pool.ntp.org as my setting in Windows' sync, and a registry tweak to synch the clock several times per day.

This is likely irrelevant as your cable box no doubt gets accurate time from the cable (?).

Your cell phone time is probably pretty accurate too - based on GPS (minus leap-seconds to UTC).