<br><br><div class="gmail_quote">On Sun, Jan 25, 2009 at 7:21 PM, Kevin J. Cummings <span dir="ltr"><<a href="mailto:cummings@kjchome.homeip.net">cummings@kjchome.homeip.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Phil Bridges wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You don't want to scan for ATSC channels if you're connected to the<br>
cable - you want to scan for QAM channels.<br>
</blockquote>
<br></div>
Incorrect statement. ATSC includes both QAM and 8VSB (which is the OTA encoding). You probably mean that he doesn't want to scan for 8VSB, but for QAM instead.<br>
<br>
But, I cannot find any information from the OP (except his vague ATSC reference) on *where* he is on order to advise him on possible protocols to check for....<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If you do want to scan for cable channels, try bypassing your converter box.<br>
</blockquote>
<br></div>
Do we know what the output of his convert box is? Analog or digital?<br>
(Is he trying to plug an analog input into a digital encoder card?)<br>
If his cable is encoded, is it worth trying to scan it directly for channels? It will tell him which channels are available, and also which are encoded.<br>
<br>
If he is scanning for channels at the output of his convert box, he won't find any (will he?) What *is* the output of his converter box?<br>
(Sorry, I'm repeating myself.)<br><font color="#888888">
</font></blockquote><div><br>i dont think you want to scan for channels. you want to fetch channel listings. <br></div></div>