Opened 14 years ago
Closed 14 years ago
Last modified 14 years ago
#1719 closed defect (fixed)
EIT data off by 1 second
| Reported by: | Owned by: | danielk | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | mythtv | Version: | |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
I was getting time data from EIT slightly off:
1092 2006-04-22 14:00:01 2006-04-22 15:00:00 Smallville 1092 2006-04-22 13:00:01 2006-04-22 14:00:01 Soul Train 1092 2006-04-22 00:30:01 2006-04-22 01:00:01 The Drew Carey Show
In EITFixUp::TimeFix?(), dt.addSecs() returns a QDateTime with the adjusted time but leaves the existing object unchanged. The attached patch fixes this.
Attachments (1)
Change History (3)
Changed 14 years ago by
| Attachment: | eithelper.TimeFix.diff added |
|---|
comment:1 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 Changed 14 years ago by
(In [9782]) References #1719. Update initial GPS to UTC offset in MythTV to current offset.
On Jan 1st, 2006 the International Earth Rotation Service added a leap second to UTC, but GPS has a fixed offset from TIA time and does not add leap seconds, hence the need for the adjustment. This is the 14th leap second added since the GPS epoch on Jan 6th, 1980.
See http://maia.usno.navy.mil/ser7/tai-utc.dat for a TIA-UTC table that goes back to 1961.
Note: See
TracTickets for help on using
tickets.
(In [9781]) Closes #1719. Fixes a bug in EITFixUp::TimeFix?(), that prevented the fix from being applied.
TimeFix? is needed because some broadcasters have not yet adjusted to the new GPS offset of 14 seconds, as opposed to the 13 second offset that has been in effect for the last few years.