Daylight savings time 2007

[kayak4ever]

For the last two time changes, it turned out that I had wanted to record a show in the 2-3 am timeslot and each one failed. The first time, the show started to record at 2a.m., the computer advanced the clock by 1 hour so I ended up with a 30 second show. The second time, I think I had no pre-recording padding such that the computer never experienced the moment that was 2a.m. so it never recorded the show. This time, I am trying an experiment to avoid this problem. I have added 5 minutes pre-padding to make sure that the show starts to record and I have added 60 minutes post-padding to make sure that it tapes for one hour commencing at 2a.m. I have also scheduled a show that is scheduled to commence at 3.a.m.. When in doubt, GBPVR should ignore the post padding of 60 minutes and start to record the 3a.m. show immediately after the time change when 2a.m. becomes 3.am. The question is what happens to the shows that are scheduled to be shown in the one hour that will effectively not exist?

I will let you know what happens with the taping.

[kayak4ever]

I agree, it probably is a fault of the epg supplier and the networks. If the hour between 2 and 3 will not really exist in the spring and there is a extra 60 minutes of time occurring, what does it mean when the networks schedule a program for that hour in the spring and what do the networks plan to broadcast during the second 60 minutes occuring beween 1 and 2 in the fall?

Anyway, thanks for the comment on how the computer clock deals with the time change. I was using XP so I may have misdiagnosed why the program recorded was so short! The main reason for my post was to alert anyone who really wants to record a 2a.m. show that they need to think about how the computer will respond in advance. Whether I get the results I expect or not, I will be closer to dealing with recording shows in the future for that specific time period (I recognize that is generally not the prime time for the most interesting shows but I want to be ready for next time)

[User]

If you know you have a show scheduled for 2am then that is the default time for DST adjustment. You can change this with TZedit to 1am, or a time when you don't have a show scheduled to start, and your problem would be solved.

http://forums.nextpvr.com/showthread.php...ght=TZedit

[baj1]

On my GBPVR PC I had "Automatic Updates" turned on so I thought I was covered with the DST change. Well, the time didn't change. so I downloaded the patch from MS and applied it. I ran an EPG update (using Zap2It), but schedule was still an hour behind. I rebooted the PC, re-ran EPG Update, but it's still off. The weird thing is that a 2 hour program is shown as two separate shows. When highlighted, the white outline is has the correct time frame for the selected show, but the descriptions are off by an hour.

Any ideas?

Thanks,
-Brad

[sub]

On my GBPVR PC I had "Automatic Updates" turned on so I thought I was covered with the DST change. Well, the time didn't change. so I downloaded the patch from MS and applied it. I ran an EPG update (using Zap2It), but schedule was still an hour behind. I rebooted the PC, re-ran EPG Update, but it's still off. The weird thing is that a 2 hour program is shown as two separate shows. When highlighted, the white outline is has the correct time frame for the selected show, but the descriptions are off by an hour.

Any ideas?

Thanks,
-Brad

Do an 'empty epg' followed by an 'update epg'.

[baj1]

That fixed it. Thanks!

-Brad

[zehd]

Isn't that a fault of your EPG supplier? The show really went from 2am-4am.

Also, whilst I don't know whether this changed in XP and I never saw it in action in '95, but the desciption of how windows handled the transition was that for going forwards an hour. Windows clocks 2 seconds for every second for 60 minutes. Similarly to go back an hour it would clock over 1 second every 2 seconds.

I was up watching the time change. (nothing else to do.)

My xp clock went 1:59:57, 58, 59, 3:00:00....

And yes my epg was screwed up. If I wanted to record something then I would have had trouble...

It looks like it's all OK in the morning though... I remember working the night shift a year ago during the last time change. All the clocks changed, and then the phones started....

It's probably the EPG company. But for 363 days a year, it works well and it's free, so no complaints...

[zehd]

Hey sub, you have daylight savings time in NZ?

[sub]

Hey sub, you have daylight savings time in NZ?

Yes we do, but GB-PVR doesnt know anything about daylight savings or when it is in effect. It doesnt need to. It stores everything as local times.

When GB-PVR is importing the listings it asks Windows to convert each of the date/times into a local time, then saves it in the database. For example, a few days ago GB-PVR might have asked Windows to convert "UTC 2007-3-12 14:30" into a local date, and if Windows had lived up to its end of the bargain, it'd do that correctly taking into account whatever timezone and daylight savings rules would apply at "UTC 2007-3-12 14:30".

In the first year of GB-PVR's life I tried to way over complicate this stuff (and had a few rough daylight savings transitions), before eventually realising it was actually pretty simple from GB-PVR point of view.

[zehd]

Yes we do, but GB-PVR doesnt know anything about daylight savings or when it is in effect. It doesnt need to. It stores everything as local times.

When GB-PVR is importing the listings it asks Windows to convert each of the date/times into a local time, then saves it in the database. For example, a few days ago GB-PVR might have asked Windows to convert "UTC 2007-3-12 14:30" into a local date, and if Windows had lived up to its end of the bargain, it'd do that correctly taking into account whatever timezone and daylight savings rules would apply at "UTC 2007-3-12 14:30".

In the first year of GB-PVR's life I tried to way over complicate this stuff (and had a few rough daylight savings transitions), before eventually realising it was actually pretty simple from GB-PVR point of view.

Instead of blaming Windows, let's cut to the chase and blame BG.

Actually I was just making conversation, wondering what's it like down there...