[mythtv] Problems with QAM scanning on Air2PC

[Jarod Wilson]

On Saturday 19 February 2005 07:33, thor wrote:
> Probably for Taylor:
>
>  Snippet of console output from setup program scanning for channels (in a
> part of the channels where there is some actual QAM):
>
> 2005-02-19 10:22:39.152 DVB#0 Signal Locked
> 2005-02-19 10:22:39.311 DVB#0 DVB signal fa20 | snr d976 | ber 6c58 | unc  
>  f 2005-02-19 10:22:39.311 DVB#0 Status: LOCK.
> Setting currenTID = 47
> 2005-02-19 10:22:44.422 DVB#0 DVB signal fff0 | snr  0 | ber    0 | unc   
> 0 2005-02-19 10:22:44.477 DVB#0 Signal Lost
> 2005-02-19 10:22:44.725 DVB#0 Status: LOCK.
> Setting currenTID = 48
> 2005-02-19 10:22:44.731 DVB#0 Signal Locked
> 2005-02-19 10:22:49.836 DVB#0 Signal Lost
> 2005-02-19 10:22:50.090 DVB#0 Signal Locked
> 2005-02-19 10:22:50.348 DVB#0 DVB signal fb30 | snr dc08 | ber  228 | unc  
>  e 2005-02-19 10:22:50.348 DVB#0 Status: LOCK.
> Setting currenTID = 49
> 2005-02-19 10:22:55.459 DVB#0 DVB signal  0 | snr  0 | ber    0 | unc    0
> 2005-02-19 10:22:55.460 DVB#0 Signal Lost
> 2005-02-19 10:22:55.714 DVB#0 Signal Locked
> 2005-02-19 10:22:55.762 DVB#0 Status: LOCK.
> Setting currenTID = 50
> 2005-02-19 10:23:00.874 DVB#0 Signal Lost
> 2005-02-19 10:23:01.383 DVB#0 Signal Locked
> 2005-02-19 10:23:01.383 DVB#0 DVB signal fb40 | snr dcc4 | ber  108 | unc  
> 10 2005-02-19 10:23:01.384 DVB#0 Status: LOCK.
> Setting currenTID = 51
>
>
>  The dtv_multiplex table gets populated, but after the scan there are
> simply no channels listed. As I mentioned on IRC, I have a standalone
> samsung HDTV box, so I know that QAM is working on the cable.
>
>  You probably need more output than that, but it's not immediately obvious
> to me what I need to do to SIPARSER() and SISCAN() defines in the .h's to
> make them produce more output.

I'm in exactly the same boat. When I use azap w/the QAM256 channels.conf, it 
shows locks on all the channels I'd expect to see locks on (and then some), 
but when running a scan from Myth's setup util, just like thor, I repeatedly 
get this on the console:

[...]
Setting currenTID = 29
2005-03-09 21:59:07.800 DVB#0 Signal Lost
2005-03-09 21:59:07.802 DVB#0 DVB signal  0 | snr  0 | ber    0 | unc    0
2005-03-09 21:59:08.306 DVB#0 Signal Locked
2005-03-09 21:59:08.405 DVB#0 Status: LOCK.
Setting currenTID = 30
2005-03-09 21:59:13.618 DVB#0 Signal Lost
2005-03-09 21:59:13.723 DVB#0 DVB signal fa10 | snr d976 | ber 4378 | unc    f
2005-03-09 21:59:13.723 DVB#0 Status: LOCK.
Setting currenTID = 31
2005-03-09 21:59:13.871 DVB#0 Signal Locked
2005-03-09 21:59:18.836 DVB#0 DVB signal fff0 | snr  0 | ber    0 | unc    0
2005-03-09 21:59:18.930 DVB#0 Signal Lost
2005-03-09 21:59:19.138 DVB#0 Status: LOCK.
Setting currenTID = 32
[...]

And the results for known-good channels say scanning timed out.

I know the channels w/something other than 0 for unc are said to be 
problematic, but I don't have a clue why the other channels aren't getting 
picked up by setup.

Is this possibly one of the issues some of the recently-sent-to-the-dev-list 
DVB scanwizard clean-up patches should address? Back to it, will probably 
give a few of 'em a shot this weekend if nobody knows. :-)

-- 
Jarod Wilson
jarod at wilsonet.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mythtv.org/pipermail/mythtv-dev/attachments/20050309/59c7652b/attachment.pgp