On 21/04/06, <b class="gmail_sendername">Stuart Auchterlonie</b> <<a href="mailto:stuarta@squashedfrog.net">stuarta@squashedfrog.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, Apr 21, 2006 at 09:26:55AM +0100, RoboJ1M wrote:<br>> Hi,<br>><br>[snip]<br>><br>> 3) UPDATE the networkid and transportid in the database.<br>><br>> I can't tune to any of the radio channels or MHEG channels on one of the
<br>> multiplexes, so that I couldn't fill in. But EIT seems to be going into the<br>> database now.<br>><br>> Is this a bug? Or is it a limitation of using channels.conf and not the<br>> scanning code?<br>
> Whatever it is, it seems ot only affects a small amount of users. One of<br>> those bugs I guess. ¬¬...<br>><br><br>This is a limitation of using channels.conf. It doesn't have all the<br>information required to completely setup the tables. Enough information
<br>to make the channels watchable, just not enough to allow EIT to work.<br><br>What you have done is a workaround that is required if you use<br>channels.conf<br><br><br>Stuart</blockquote><div><br>Yeah, I thought as much.
<br>Just out of interest, where does the networkid and transportid come from?<br>Is there any way to get it apart from the workaround stated?<br><br>Thanks,<br><br>J1M.<br> </div><br></div><br>