<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Apr 7, 2006, at 9:37 AM, Greg Grotsky wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">All,<BR> <BR> I think it's a bug in myth. Here are some screen shots for the following experiment...<BR> <A href="http://www.spartanframeworks.com/Spikey/ScreenShot-Working_845AM_after_running_--refresh-all.gif">http://www.spartanframeworks.com/Spikey/ScreenShot-Working_845AM_after_running_--refresh-all.gif</A><BR> <A href="http://www.spartanframeworks.com/Spikey/ScreenShot-Working_915AM_after_waiting_30_minutes.gif">http://www.spartanframeworks.com/Spikey/ScreenShot-Working_915AM_after_waiting_30_minutes.gif</A><BR><BR> 1) At 8:45ish I noticed that tonights programming information was an hour early. So I ran "mythfilldatabase --refresh-all"<BR> 2) It corrected the programming information (as seen in 845AM screenshot)<BR> 3) At 9:15ish I check the program guid again and the info was shifted by an hour again. (see 915AM screenshot)<BR> <BR> I have a theory about what's going on here. I think that when I run "mythfilldatabase --refresh-all" it's correcting the information in the DB. However, when the time change happened I had several recordings scheduled to be recorded into the next week... I'll bet these "recording times" are stored by the backend and are somehow getting written over the "good" database information. I don't know enough about it to point to a piece of code, but I'm hoping that someone else who does know sees this email. :)<BR> <BR> I have noticed that if I browse very far out, like into next week, all the timestamps look correct. I know this is not a zap2it issue because when I run "mythfilldatabase --refresh-all" it's getting the correct information.<BR></BLOCKQUOTE><BR></DIV><DIV>That begins to make sense. My setup is essentially the same as yours, right down to the timezone (I'm in Cheyenne).</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>But, at the time of the DST change, I think I had perhaps one recording scheduled that was after the change. Being a paranoid type I intentionally tried to not schedule anything after the change until it happened.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I did have a couple of "glitches" with recordings that were happening at the exact time of the change, but that didn't surprise me and it is not the problem you're having.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I suppose you could delete all of your scheduled recordings and re-schedule them. DST has always been problematical for broadcasters, although normally the "extra hour" was more hassle than the "missing" one.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>There should be a DST section in the WiKi, if I can accumulate enough info I'll be happy to write it up, so please post whatever your final answer turns out to be.</DIV></BODY></HTML>