<br><div class="gmail_quote">On Wed, Jun 22, 2011 at 10:00 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 06/21/2011 07:21 PM, Troy Dack wrote:<br>
> As for the time offset, comparing the data in the dvbsnoop dump and what C31<br>
> have on their web site for upcoming programs it looks like they are actually<br>
> sending out correct UTC times.<br>
><br>
> It seems that EITHelper is failing to extract any data for this particular<br>
> channel and I can't work out why.<br>
<br>
</div>Rescan the transport?<br>
<br>
Mike<br>
<div><div></div><br clear="all"></div></blockquote></div><br>I deleted the channel and transport from mythtv-setup then checked in the database to make sure it was gone, all good so far.<br><br>Do a channel re-scan from mythtv-setup, the channel is picked up and I told setup to automatically add it and update all other channels that is found too.<br>
<br>Channel appeared in the list, I changed the allocated channel number, added an icon and ticked "Use on air guide data". There is no xmltv id set for this channel.<br><br>Exited setup, restarted backend and added eit and siparser to logging.<br>
<br>Still no EITScanner or EITHelper messages that appear to relate to the channel missing EIT information. The eit_cache table doesn't have any entries for this channel either.<br><br>-- <br> <a href="mailto:troy@tdack.com">troy@tdack.com</a><br>