Mmmm, more than 12 months later - are we any closer guys?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: tonymy01 on October 12, 2008, 11:54:03 PM
I think the best solution is for ICE to send the timers as UTC (as their whole database for EIT is UTC which is the correct standard for EIT anyway), but to also include a GMT offset parameter with the timer data, and then the PVR can much more simply just add the offset if the PVR stores timers in localtime, then everyone is happy.
Then all you need is for the PVR to correctly adjust its clock at the right time, and then everything will be in order.
Quote from: tonymy01 on October 10, 2008, 07:28:07 PM
When we complained about the timers being one hour out, ICE said it was because the Beyonwiz wasn't DST aware. Thus I have to assume they send the timers as GMT, as there is no other way this problem could happen (as once the timers are created, the Wiz stores them in local time too, thus why my own daily timer didn't alter by one hour when I fixed the GMT offset for the clock).
I am guessing your statement was somewhat rhetorical, possibly questioning the way ICE does things.
The good thing about being GMT for timers is there is no question about what to do at 2am Sunday morning of the DST transition (as there is two 2ams when DST ends). But I reckon for sure they should also provide the GMT offset to the timers in the protocol also, so that PVRs don't have to have a tonne of logic to apply different rules when creating timers before and after a transition.
Regards
