2005-07-08, 07:56 AM
The times that Zap2it Labs gives for my programs are all an hour off. Here's what they have to say about it:
------------------------
All schedule air dates in the XTVD data from DataDirect are supplied in UTC (Greenwich Mean Time), which is fixed and does not change with Daylight Savings. Therefore, all time offset issues result from misconfiguration in a client using DataDirect.
Many Zap2it Labs users use XMLTV to access the DataDirect service, which requires a user to properly set the time offset. In the current version of XMLTV, this is set in the initial client configuration by running xmltv tv_grab_na_dd --configure, which writes the time offset to the tv_grab_na_dd.conf file. Users of older XMLTV versions may use the "--offset" command-line flag flag to set the offset. Whatever the method, if this is set improperly, then the XMLTV file created from the DataDirect XTVD data will have improper schedule times.
----------------------------------
What I would like is either an internal fix for this or the ability to tell GB-PVR to asjust all the times given by the guide by a given amount of time (an hour is probably all that would be needed given the situation). The other option would be to just have a setting that tells it to adjust its internal time by an hour and you'd just have to be aware that all the times that you were dealing with were an hour off.
As it is, I have to input manual timers for everything since the times are all off. I don't know which solution to the problem would be the best, but one that results in the guide giving the correct times would be preferable. Regardless, a fix for this would be quite desirable. It would cause too many problems for me to offset my system clock by an hour to get GB-PVR to record at the correct time, so that's not a good solution for me.
GB-PVR is a great program. Thanks a bundle. But it would be nice if this scheduling problem peculiar to Zap2it could be fixed. Thanks.
------------------------
All schedule air dates in the XTVD data from DataDirect are supplied in UTC (Greenwich Mean Time), which is fixed and does not change with Daylight Savings. Therefore, all time offset issues result from misconfiguration in a client using DataDirect.
Many Zap2it Labs users use XMLTV to access the DataDirect service, which requires a user to properly set the time offset. In the current version of XMLTV, this is set in the initial client configuration by running xmltv tv_grab_na_dd --configure, which writes the time offset to the tv_grab_na_dd.conf file. Users of older XMLTV versions may use the "--offset" command-line flag flag to set the offset. Whatever the method, if this is set improperly, then the XMLTV file created from the DataDirect XTVD data will have improper schedule times.
----------------------------------
What I would like is either an internal fix for this or the ability to tell GB-PVR to asjust all the times given by the guide by a given amount of time (an hour is probably all that would be needed given the situation). The other option would be to just have a setting that tells it to adjust its internal time by an hour and you'd just have to be aware that all the times that you were dealing with were an hour off.
As it is, I have to input manual timers for everything since the times are all off. I don't know which solution to the problem would be the best, but one that results in the guide giving the correct times would be preferable. Regardless, a fix for this would be quite desirable. It would cause too many problems for me to offset my system clock by an hour to get GB-PVR to record at the correct time, so that's not a good solution for me.
GB-PVR is a great program. Thanks a bundle. But it would be nice if this scheduling problem peculiar to Zap2it could be fixed. Thanks.