[mythtvnz] EPG Data for 'niche' channels ?

[Nick Rout]

On Fri, May 11, 2012 at 2:01 PM, Nick Rout <nick.rout at gmail.com> wrote:
> On Fri, May 11, 2012 at 12:52 PM, David Moore <dmoo1790 at ihug.co.nz> wrote:
>> On 11/05/12 12:21, Nick Rout wrote:
>>>
>>> On Fri, May 11, 2012 at 11:43 AM, Steven Ellis<steven at openmedia.co.nz>
>>>  wrote:
>>>>
>>>>
>>>> On Thu, May 10, 2012 6:26 pm, David Moore wrote:
>>>>>
>>>>> On 10/05/12 17:18, Steven Ellis wrote:
>>>>>>
>>>>>>
>>>>>> On Thu, May 10, 2012 3:14 pm, David Moore wrote:
>>>>>>>
>>>>>>> On 10/05/12 09:07, Steven Ellis wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi David. In your MythTV setup for the freeview source what time zone
>>>>>>>> do
>>>>>>>> you set for the EPG. In my case I default to using AUTO as I import
>>>>>>>> multiple EPG feeds for different timezones, for example SBS (now
>>>>>>>> sadly
>>>>>>>> off
>>>>>>>> air).
>>>>>>>>
>>>>>>>> When I generate listings with epgsnoop the data contains the +1200
>>>>>>>> offset
>>>>>>>> based on my local system vs the DVB data.
>>>>>>>>
>>>>>>>> In the case of DTT I merge DVB and MHEG data so that my DTT and DTH
>>>>>>>> channels are being provided with identical EPG information. For the
>>>>>>>> DTT
>>>>>>>> exclusive channels I just pull them from the MHEG file using tv_split
>>>>>>>> and
>>>>>>>> tv_cat.
>>>>>>>>
>>>>>>>> Steve
>>>>>>>>
>>>>>>> Hi Steve. My setting is "none" for the EPG timezone. I only have DVB-T
>>>>>>> so it works fine with the MHEG EPG local times. I'll probably do a
>>>>>>> quick
>>>>>>> fix just for you :) that gives you the option to generate UTC +1200
>>>>>>> (or
>>>>>>> +1300 for DST). Then I'll think about a more general solution. /David
>>>>>>>
>>>>>>
>>>>>> Dave. That would be brilliant. Cheers
>>>>>> --------------------------------------------
>>>>>> Steven Ellis - Technical Director
>>>>>> OpenMedia Limited - The Home of myPVR
>>>>>> email   - steven at openmedia.co.nz
>>>>>> website - http://www.openmedia.co.nz
>>>>>
>>>>>
>>>>> Version 0.3.4 just uploaded. Turned out to be not so simple because (a)
>>>>> I decided to try and do it right rather than quick and dirty and (b)
>>>>> surprisingly Python doesn't do time zones very well. Anyway I think it
>>>>> works. Just add "-z" command line arg. Enjoy.
>>>>>
>>>>
>>>> Nice try but times are off by a couple of hours.
>>>
>>>
>>> 12 hours isn't it? (one says 0600 hours or 6am, t'other says 1800 or 6pm)
>>>
>>>>
>>>> For example take from DVB-S i get
>>>>
>>>> <programme channel="1035.dvb.guide" start="20120512180000 +1200"
>>>> stop="20120512190000 +1200">
>>>>        <title lang="eng">ONE News At 6pm</title>
>>>>        <desc>The nation's leading team of journalists brings viewers the
>>>> latest news and sport, plus the most comprehensive weather
>>>> report.</desc>
>>>>        <category>tvshow</category>
>>>>        <category>News/Current Affairs</category>
>>>>        <!-- Cat:2-0 -->
>>>>        <!-- Unknown rating:0 -->
>>>> </programme>
>>>>
>>>>
>>>>  From MHEG I get
>>>>
>>>>        <programme channel="1200.dvb.guide" start="20120511060000 +1200"
>>>> stop="20120511070000 +1200">
>>>>                <title>ONE News At 6pm</title>
>>>>                <desc>The nation's leading team of journalists brings
>>>> viewers the latest news and sport, plus the most
>>>> comprehensive weather report.</desc>
>>>>                <episode-num system="dd_progid">10272257</episode-num>
>>>>                <subtitles type="teletext" />
>>>>        </programme>
>>>>
>>>> Cheers
>>>>
>>>> Steve
>>>>
>>
>> Well it looks like the DVB-S date/time is wrong to me. The UTC time for news
>> at 6 pm should be 2012mmdd060000 because we're 12 hours ahead of UTC.
>
> No no no, the timezone is +1200 and the date/time is specified in the
> that timezone, in other words 1800 hours NZ time (which is 1200 ahead
> of UTC).


For example here is the output of date -R on my pffice server just a
minute or so ago:

nick at server:~$ date -R
Fri, 11 May 2012 14:02:37 +1200