2010-11-03, 00:04
right, this is strange.
it only uses an offset if the local time and backend time are different (more than 30 minutes). those times will only be different if an offset is used and that will only be used if tvheadend tells us to use it.
the only other reason I can think of is that CDateTime::GetCurrentDateTime().GetAsTime(localTime); in xbmc returns something else than gettimeofday() which tvheadend uses.
I'll add some configurable offset correction later as someone suggested and will put the values that tvheadend reports in the log. that will solve these issues, even if one of the systems is configured incorrectly.
edit:
both have been implemented and been commited to git. new builds will follow later this week.
it only uses an offset if the local time and backend time are different (more than 30 minutes). those times will only be different if an offset is used and that will only be used if tvheadend tells us to use it.
the only other reason I can think of is that CDateTime::GetCurrentDateTime().GetAsTime(localTime); in xbmc returns something else than gettimeofday() which tvheadend uses.
I'll add some configurable offset correction later as someone suggested and will put the values that tvheadend reports in the log. that will solve these issues, even if one of the systems is configured incorrectly.
edit:
both have been implemented and been commited to git. new builds will follow later this week.