id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	mlocked
2143	ATSC EIT time offset is incorrect	anonymous	danielk	"I am having a program with my EIT guide data being offset by 2 hours. I am using a DViCO FusionHDTV5 Gold USB on Fedora Core 5. I live in Los Angeles and am using the DViCO to receive OTA HDTV. I am running svn trunk 10721. 

I added the follow line in EITHelper::CompleteEvent(...) to aid in debugging:
    VERBOSE(VB_EIT, LOC + QString(""event:%1 event.start_time:%2 localstarttime:%3 utc_offset:%4"")
            .arg(event.title).arg(event.start_time).arg(starttime.toTime_t()).arg(utc_offset));

When running the backend I get:
2006-08-09 09:38:00.833 EITHelper: event:Fox 11 Morning News at 6 AM/Good Day L.A. event.start_time:839336414 localstarttime:1155294000 utc_offset:-25200
2006-08-09 09:38:00.885 EITHelper: event:Fox 11 Morning News at 5:00 AM/Good Day L.A. event.start_time:839332814 localstarttime:1155290400 utc_offset:-25200

doing the math...
seconds per day: 86400
leap seconds since gps epoch: 14

for the first show:
based upon the eit raw data, (839336414-14-25200)%86400/60/60 = 6
based upon the calculated local starttime: (1155294000-25200)%86400/60/60 = 4

for the second show:
based upon the eit raw data, (839332814-14-25200)%86400/60/60 = 5
based upon the calculated local starttime: (1155290400-25200)%86400/60/60 = 3

I believe that these should be equal. It looks like it may be something with the qt lib. for reference:
# rpm -qa |grep qt
qt-MySQL-3.3.6-0.4.fc5
qt-3.3.6-0.4.fc5
qt-devel-3.3.6-0.4.fc5


Thanks, let me know if I can provide more information..
"	patch	closed	minor	0.20	mythtv	0.20	medium	fixed	eit		0