On 4/16/07, <b class="gmail_sendername">R. G. Newbury</b> <<a href="mailto:newbury@mandamus.org">newbury@mandamus.org</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;">
<snip><br>There is one slightly difficult bit: Not in getting the hardware to<br>work, but in matching it to your cable lineup (see below).<br>The hardware side is dead easy.</blockquote><div><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<snip><br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">So although myth can identify 'a' channel, at 74#3 it has NO knowledge
<br>about how that stream is identified at zap2it. It is up to the user to<br>determine that the one originally called '74#3' is really described as<br>125 by your cablco....and that 125 is xmltvid 10123, callsign WXYZ.
<br><br>Once you tell myth that you want the channel tuned at 74#3 described as<br>'Channel 125' and 'WXYZ' (as listed by zap2it) it knows how to pull down<br>the listings for the channel, and to tune that channel when requested.
<br><br>Now whether the mythfilldatabase listings actually match the tv<br>listings, and whether you have actually discovered the correct channel<br>are......unknown...</blockquote><div><br>Gee whiz, this is unintuitive. Have there been any discussions on making this easier for end users? Could we start a central repository of geographical mappings based on each service provider so only one poor soul has to go through this pain? I wonder if Zap2It could be expanded to provide this mapping for us...
<br><br>/Brian/<br><br></div></div>