EPG start/end times out by a minute or two

[Jim_]

Thanks for the help guys, it’s working now.
I’m not sure what caused it because daylight savings isn’t until next Sunday, and my clock was properly configured to adjust for the time change automatically.
I found a post recommending CleanXMLTV for almost any XMLTV problem.
It converted UTC to +0000, and the following epg update went fine.

[Snarky]

I'm sticking by my original comments. There is nothing in GB-PVR that would do this.

I've just experienced a problem somewhat similar to what reven reported back then, with GBPVR giving the wrong start and end times for shows even though the data is correct in the database.

I'm using EPG data from Zap2It. I have a plugin that displays Programme objects in a program guide format. However, the start times and end times reported by the Programme objects are incorrect by a range of about +/- 2 minutes. For example, one show starts at 11 PM and ends at midnight, but when I call getStartTime() and getEndTime() on it, the DateTimes I get back are:

Start 5/9/2007 22:59:02.2720000
End 5/10/2007 00:00:12.2880000

As you can see, the offset is irregular, and down to milliseconds. Interestingly, the preceeding and following shows match these numbers exactly, so that all programs are continuous. If I query the database myself, I get back the correct values. This problem doesn't appear to affect GBPVR internally, as the built-in program guide has the correct info.

The affected Programme objects have all been created or retrieved by calling GBPVR.Backend.Common.ScheduleHelper.getInstance().GetProgrammeByOID(); and have definitely not been tampered with since then.

Finally, this occurs with data that is stored in the Access mdb file. When I convert to SQLite db3, it doesn't happen (so far). But should it reappear at any time, maybe this information will be helpful in tracking down the problem.

[sub]

Finally, this occurs with data that is stored in the Access mdb file. When I convert to SQLite db3, it doesn't happen (so far). But should it reappear at any time, maybe this information will be helpful in tracking down the problem.

Probably some bug in the OleDB driver for Access. This isnt a concern to me these days though - SQLite is the default for all installs, and the only database I test.