[mythtv-users] Fwd: Re: channel4 hd has no eit - cross-eit

Mike Perkins mikep at randomtraveller.org.uk
Mon Sep 6 08:32:23 UTC 2021

On 06/09/2021 07:09, UB40D via mythtv-users wrote:
> On Sun, 5 Sept 2021 at 11:46, Stephen Worthington <stephen_agent at jsw.gen.nz>
> wrote:
>> And for the purposes of cross-eit.py, MythTV uses only UTC internally.
>> Mythfilldatabase will convert local times to UTC when it reads XMLTV
>> data.  So all cross-eit.py need to do is to add " +0000" to the end of
>> each "start=" and "stop=" field and that should make that warning
>> message go away.  In any case, it is just a warning and can be ignored
>> as mythfilldatabase is correctly assuming that the timestamps are UTC.
> Err... either I can't understand what you are saying or some part of the
> above is factually incorrect (or maybe does not apply to my setup).
> I have experimentally observed the listings produced by cross-eit causing
> recordings to miss one hour (either at the start or at the end, depending
> on the direction of the mistake) if the one-line fix by John was not
> applied at the right time of year.
It may depend on how your system clock is set. Have you configured it for UTC or for local time? If 
the latter, then I would expect to see the effects you describe.

Whenever I install a new system (which is far too frquently these days) hardware RTC setting is one 
of the questions Debian asks. All my boxes are set to UTC. I have no problems displaying times 
according to local requirements and I have never had any issues with mythtv.


Mike Perkins

More information about the mythtv-users mailing list