Griga Posted October 26, 2010 Share Posted October 26, 2010 ..the DVBViewer should take the TOT into account Not possible, because this information is not available on all transponders resp. in all networks, thus preventing a unique handling of all EPG data (which is mandatory). Additionally the local transition date (where the PC is located) may differ from the one indicated by the Local Time Offset Descriptor. However, it may be worth considering to use the according localized information provided by Windows: http://msdn.microsoft.com/en-us/library/ms725481%28VS.85%29.aspx Quote Link to comment
uglyned Posted October 27, 2010 Author Share Posted October 27, 2010 EPG times are broadcasted as UTC and DVBViewer adds the current local time offset (as provided by Windows) to all of them, which means, the Sunday EPG times are displayed with today's time offset. It will change on Sunday. True, but unless it's changed since last time, all the recordings in the Recording Service timer list that have been added by the auto timer task will not be updated, and the first time the auto timer task runs after the time change, duplicates will be created for all of them. Usually I just delete the whole timer list then run the task again. It seems easier than trying to fix it. I just have to remember if there are any manually added timer events in there. Quote Link to comment
Soupdragon Posted November 8, 2010 Share Posted November 8, 2010 Thanks for this! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.