2011-10-21, 06:58
tsp42 Wrote:I reset the PVR database. Afterwards the end time in the EPG was set to 1671 something as you also reported. I will look further into it tomorrow. It doesn't happen in windows and I mainly developing the add-on in visual c++ so it takes a little more effort to debug in kdevelop.
By the way, dushmaniac requested I file a detailed bug report with logs, so I I've filed it at github here:
https://github.com/opdenkamp/xbmc/issues/277
And after some trial-and-error. I found a (partial) solution (also posted here: https://github.com/opdenkamp/xbmc/issues...nt-2478152 )
I noticed that all the EPG events themselves are stored within the PVR add-on in UTC but the EPG cleanups, i.e. the timestamps about when to refresh the EPG data itself are done in local time, that is, all except one place where UTC was used in place of local time. in CEpgContainer::UpdateEntry, the NextEpgUpdate variable is populated using the UTC (rather than local time), creating a skew, meaning the event window doesn't get populated. The following patch fixed it for me:
https://gist.github.com/1303227
However, I still have some clock skew events like Jimmer has reported, where the events are off by an hour in the timeline grid, but appear Ok when you look at the detailed view.