Drifting Clock issue closed?

[Orient Express]

I have not seen any complaints about the clock drift issue on the HR2X lately. Is it safe to assume that recent releases have fixed the issue?

[LarryFlowers]

The problem if it existed in any great numbers, hasn't generated any complaints in a long time so I would suspect it is gone... are you having an issue? If you are have you reported it?


I have not seen any complaints about the clock drift issue on the HR2X lately. Is it safe to assume that recent releases have fixed the issue?

[JTAnderson]

It disappeared for me two or three software releases ago.

[Ken S]

They didn't really fix the clock what they did is to put automatic padding around all the shows. It solves the problem unless you start getting show cancellations because of overlapping record times.

[DonHac]

It's not just the extra padding - I think they actually fixed the problem. I used to have an annoying amount of clock drift, but I haven't had a problem in months. If it were just the extra padding I'd have to back up to catch the beginning of shows, and I don't. My benchmark is the local 5pm news, where the newsroom clock is visible in the background, and the playback has been starting when that clock shows 5:00:01. Either my hardware got better or the software did. I'll take my bets and say Thank You to the DirecTV programmers.

Don

[TomCat]

It would seem that it would be easy to fix. If the local clock is free-running and is fast or slow, an NTP daemon, or ntpd can auto-correct that (not fix the drift, per se, but resync the time to the NTP server on occasion). It seemed that for some time the daemon was only checking/correcting the time infrequently, like possibly once a day during the EPG downloads, for instance. A simple fix would be to have it fire off more often, such as every time the unit is turned on, or every time a recording is pending in the next few minutes. A couple lines of code in a NR could make that happen, and my best guess is that it probably did.

Even though the fix was probably easy, the time frame was slow due to the huge laundry list of issues that dominated things early on. Pure speculation, of course.

[jcc]

They need to do another software update because the clock on mine is three minutes slow and I have to keep resetting it what seems like every few days.

[Mike Bertelson]

I never really noticed it being that big of an issue in the first place. Soft padding must have took care of it for me. :shrug:

Mike

[john18]

I've had the issue on occasion, but I am usually running CE software. When I get it I have found a trick to fix it. Go to Menu > Settings > Settings > Display > Clock and set the clock for another timezone. Move back and hit Done then go put it back in the proper timezone. That has worked for me in the past.

[TomCat]

They need to do another software update because the clock on mine is three minutes slow and I have to keep resetting it what seems like every few days.It may be that the local ntpd service running on your DVR has spontaneously quit. Try a restart.