[mythtv-users] Schedules Direct and time offset

[R. G. Newbury]

Robert Eden wrote:
> On 2/27/2008 8:33 AM, Richard Shaw wrote:
>> It looks like Myth is offsetting the time by +6 instead of -6 hours
>> (which would give me the 12 hour difference from actual I'm seeing).
>> Although it should handle this properly I wouldn't be so aggravated if
>> the timeoffset field worked and I could "Tune it" to be correct.
>>   
> <programme start="20080226003000 +0000"
> is the same as
> <programme start="20080225183000 -0600"
> 
> The purpose of the XMLTV offset is to make the file more humanly readable, an application should take the provided time offset into account in it's calculations (and hopefully use GMT internally as it solves DST issues)
> 
> I often run into applications that ignore the offset field and just used the XMLTV offseted time values..... then they complain about DST issues! :)
> 
> So you're back to a MythTV problem and not a XMLTV problem. Thank you for calling XMLTV support. :)


It actually sounds more like an operating system problem. You should 
check what time system is being used. Under Fedora, you have a choice to 
have the system use UTC time, while reporting after adjusting for the 
time zone offset: files are recorded UTC but the clock shows EST for 
example.

This setup can  be confusing for myth purposes...your files are all 
timed at 3 AM to next morning for tonights 10 pm show!

Using UTC is fine for desktops and laptops, especically if you must sync 
your files, but its not so good for myth.

Set the system to use your time zone's time and let myth make the 
adjustment in the xmltv listing data (rather than 2 adjustments).

Geoff


-- 
              R. Geoffrey Newbury			

        Helping with the HTTP issue
<a href="http://www.w3.org/Protocols/">HTTP</a>