On 6/28/07, <b class="gmail_sendername">Donald J. Maddox</b> <<a href="mailto:dmaddox099@yahoo.com">dmaddox099@yahoo.com</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;">
Well, as you may recall from my original posting, it all works great<br>with other programs, just not with MythTV - so the frequency tables and<br>modulation type are definitely correct. </blockquote><div><br>I meant to check that you have them set correctly within mythtv on the channel scanning page.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I have tried with 'open DVB<br>card on demand' and without, and it makes no difference in this case.
<br>Lengthening the timeouts doesn't help either - it consistently shows 0%<br>signal on every channel, or occasionally, some random percentages, like<br>29% signal, and 4% S/N - but in those cases these random number will
<br>stay the exactly same for every channel as it scans, which doesn't even<br>make sense.</blockquote><div><br>This sounds like a driver/firmware issue, though I'm not sure why it would work with other tools and not with myth if that were the case. Did you compile from source? If so did you --enable-dvb? In your capture card setup, you select "DVB DTV Capture card (
v3.x)" correct? From what I understand the pcHDTV capture card code is broken and so users of that card should select the generic device.<br></div><br></div>-- <br>Dylan<br><br>Type faster. Use Dvorak:<br><a href="http://dvzine.org">
http://dvzine.org</a>