Originally Posted by AV Empiricist
If someone is willing to invest the time and effort to accumulate data for analysis, I'm all for it. While I appreciate their efforts and revelations, it doesn't seem to have resolved the issue for the people in Austin.
I have three Pal dvrs displaying the full DC Guide and the correct time. It's useful that J-D-H reset the DC zip this morning and gave us the results because it tends to corroborate the hypothesis: The DC zip code needs to be reset during an optimum period of day (as recommended by the guys in Austin).
So my recommendation remains: At 6PM set the zip code to 21210. The next day at 7PM, set the zip to DC and wait 7 hours.
In fact, if at 6PM the Baltimore zip resets the clock quickly, try restoring the DC zip at 7PM the same day. It's really not a big investment of effort.
Has anyone tried to set a zip code that is far from their reception area in order to force a PSIP only clock set? As a last desperate measure, this might be preferable to a crazy clock.
I believe you're correct about choosing the right time to make changes -- this factor seems to be critical here.
After observing that going to a Baltimore zip code was the only way to get get an accurate clock, I wanted to confirm this and the most straight forward way was by reverting to my old Wash DC settings. After doing this, I found out the hard way that my original conclusion seems to have been correct. After swinging the antenna to Wash DC as well as changing the zip code to Wash DC, the clock became almost instantly off by 5 minutes or so (fast). I made the changes at 6:30 PM last night, presumably around the best time. After observing the bad clock, I tried several soft-resets via the 4 sec on-off button push on the remote. This caused some minor clock changes, but certainly not a fix, not a return to an accurate clock.
Now I need to try to get back where I was, something I'll work on later today.
While making the above changes, I periodically checked how much advance TVG info was present. No matter what nor when, the listings were always limited to one day. Maybe this is a bogus observation since I probably needed to wait a few hours to be certain, but for whatever it's worth I'm still reporting what I saw.
There are quite a number of variables here (antenna bearing, zip code, which of two CBS stations are allowed in the channel listing, soft-reset or not, how long to wait between changes, etc.). And when doing tests, the order in which the changes are made matters as well as the time of day when they are done (at least for some of the changes). This leads to a test matrix which is large and rather intimidating. So if and when I can get the clock back to being accurate, whether or not advance TVG data appears, maybe I'll stop making changes for awhile. This strikes me as prudent since those in power to actually DO something to fix all this - the CBS stations and/or Rovi/TVGOS - presumably already know exactly what caused the problem in the first place. Will accumulating test results (with or without a TV tuner) to send to the only entity who has been slightly responsive, the local CBS station's tech director, even conceivably be productive? If we have zero clout as has been said here, I fear the answer to that isn't a very optimistic one. On the other hand, if there are reasons why any of these companies ~would~ care about the impact of what they've done on we DVR owners, I'd love to hear what they are....