Quote:
Originally Posted by J-D-H 
That very last bit throws me. My clock is now at least temporarily accurate via a few recent changes here, but I fear this would reverse at any time (it all depends on which of two CBS stations my DVR finds attractive to use for TVGOS data on any one day). So now I don't know whether to enable updates at 6:30 PM as you suggest, or disable it. What do you foresee possibly happening with updates enabled when the clock is at least temporarily accurate?

That very last bit throws me. My clock is now at least temporarily accurate via a few recent changes here, but I fear this would reverse at any time (it all depends on which of two CBS stations my DVR finds attractive to use for TVGOS data on any one day). So now I don't know whether to enable updates at 6:30 PM as you suggest, or disable it. What do you foresee possibly happening with updates enabled when the clock is at least temporarily accurate?
The update from Austin is that this auto-reboot method no longer works reliably so I have stopped using it. I think the timestamps must be skewed sometimes even during prime-time. I say this because even the manual intervention of changing time-zone (or zipcode) and then changing it back, no longer works reliably either. I have attempted several times in the middle of prime-time, with no affect on clock skew. I know I should fire up TSREADER to confirm what's really happening, but I haven't bothered.
What used to work in Austin is what Mark is describing to you in his post. Under those conditions, timestamps from about 5pm to 11pm were not skewed while timestamps at all other times were skewed. The clock smoothing algorithm in the DVR prevents it from taking immediate advantage of the clean timestamps starting at 5pm so what was needed was a way to force the DVR to drop its TVGOS time lock and re-acquire it during the "clean zone". This could be done manually using the zipcode or time zone trick but that required manual intervention every day sometime after 5pm but before the desired evening recordings started. Mark suggested a way to automate this process using the auto-update feature and that worked pretty well for a while...
So to answer your question, no harm will come from triggering the auto-reboots, but if you've found a solution that doesn't require it I certainly wouldn't recommend it. Also, if the WUSA clock skew issue is some completely different animal than the KEYE clock skew issue, the auto-reboot solution might not do you any good anyway. But it terms of recommended timing the auto-reboot would have to happen AFTER the "clean zone" of unskewed timestamps started (thought to be around 6:30pm now), but at least 5 min BEFORE the intended recording starts. Doing the reboot after primetime would be pointless. You might fix the clock for a brief time, but it will be hosed up again by the following morning and it will remain hosed up when your intended recordings begin that following evening. Confusing I know...

























