[mythtv] [mythtv-commits] Ticket #2780: HDTV (ATSC) tuning is not working

Daniel Kristjansson danielk at cuymedia.net
Sat Dec 23 01:19:56 UTC 2006


On Sat, 2006-12-23 at 00:15 +0000, MythTV wrote:
> #2780: HDTV (ATSC) tuning is not working
> ---------------------------------------+------------------------------------
>  Reporter:  james.meyer at operamail.com  |        Owner:  danielk 
>      Type:  defect                     |       Status:  reopened
>  Priority:  minor                      |    Milestone:  unknown 
> Component:  mythtv                     |      Version:  head    
>  Severity:  high                       |   Resolution:          
> ---------------------------------------+------------------------------------
> Changes (by newbury at mandamus.org):
>   * status:  closed => reopened
>   * resolution:  fixed =>
>   * severity:  medium => high

Some questions:
Are you scanning 8-VSB, QAM-64 or QAM-256?
What frequency table are you scanning?
What drivers are you using? (v4l or dvb)?
What version of the drivers are you using?
Has MythTV scanning ever worked you?
Some answers:
S/N ratio has always worked in MythTV, this not being reported is a
driver issue. It's also irrelevant to scanning so just ignore it.
The atsc_minor_chan column stores the ATSC Minor Channel and has no
relation the DVB Service ID. The service_id column should be set to the
MPEG program number in an ATSC scan, but this is not used for tuning so
you can ignore it.
The xmltvid has nothing to do with scanning except that it maybe
indicates you had some bogus entries in the database before you
ran the scan and need to delete your existing channels.
Your DB info looks completely bogus, here's a channel row from
my test machine:
|   1021 | 2_1     | 56     |        1 | WCBS-HD  
| WCBS-HD |      |     NULL |              | 16689   
|           0 |    32768 |      32768 |  32768 | 32768 
| ATSC     |        0 |       1 |               
|             1 |      99 |         1 |      NULL 
|        0 |               2 |               1 
| 2006-12-21 18:30:02 |
Here's the matching dtv_multiplex row:
|      99 |        1 |        NULL |      NULL 
| 725000000 | a         |          0 | auto | v        
| 8vsb       | a         | auto         | a                 
| auto           |       0 | 8vsb          | a         
| auto         | atsc       |             33 
|  20061212210854 |

Note the next to last column in my channel table vs. yours,
the atsc_minor_chan should never be less than one for an
ATSC channel.

Of course, if you are doing a QAM scan you may not be doing
ATSC tuning at all, in which case it would be your 32767
mplexid I would want to know about first.

Some logs I will need:
Run mythtv-setup with '-v record,channel,siparser' and first
set the signal timeout to 2000 msec and the channel timeout
to 10000 msec. Then do the scan with 'Delete' as the existing
channel treatment. Attach the log and dumps of the resulting
channel and dtv_multiplex entries for that sourceid to a new
ticket describing your problem.

Run the appropriate atscscan command and send me the command
line you used an the output of the scan command.

Make sure you open a new ticket as the ticket you reopened
was for a specific bug which has already been fixed and 
has nothing to do with the problem you are experiencing.

-- Daniel



More information about the mythtv-dev mailing list