[mythtv-users] HDTV and Myth Chan Scan

Mudit Wahal mwahal at gmail.com
Fri Feb 17 03:04:41 UTC 2006


Disclaimer: some experience on hdtv OTA channels on 0.18.1. Dont know
about QAM or 0.19 tables.

32767 seems like a -1 (0xffff) or a signed short (7fff), depending
upon what is being printed from the message.

Most likely an uninitialized entry for the channel table in the
dtv_multiplex. Check the frequency of the channel 213 and find the
correspondence frequency in the dtv_multiplex.
Then use that mplexid (which is the index for the channel 213 info) in
the channel table.

Thanks

Mudit

On 2/16/06, Michael Haan <michael.haan at gmail.com> wrote:
> Ok, so starting mythbackend gives me:
>
> 2006-02-16 20:33:30.363 Connected to database 'mythconverg' at host:
> localhost
> 2006-02-16 20:33:30.529 DVB#0 Using DVB card 0, with frontend 'Oren OR51132
> VSB/QAM Frontend'.
>  2006-02-16 20:33:30.530 DVB#0 ERROR - Could not find dvb tuning parameters
> for mplex 32767
> 2006-02-16 20:33:30.531 DVB#0 ERROR - Failed to get channel options for
> channel 213.
> 2006-02-16 20:33:30.533 New DB scheduler connection
>
> Not suprisingly:
>
> mysql> select * from dtv_multiplex;
> +---------+----------+-------------+-----------+-----------+-----------+------------+------+----------+------------+-----------+--------------+-------------------+----------------+---------+---------------+-----------+--------------+------------+----------------+---------------------+
> | mplexid | sourceid | transportid | networkid | frequency | inversion |
> symbolrate | fec  | polarity | modulation | bandwidth | lp_code_rate |
> transmission_mode | guard_interval | visible | constellation | hierarchy |
> hp_code_rate | sistandard | serviceversion | updatetimestamp     |
> +---------+----------+-------------+-----------+-----------+-----------+------------+------+----------+------------+-----------+--------------+-------------------+----------------+---------+---------------+-----------+--------------+------------+----------------+---------------------+
> |       1 |        2 |           0 |         1 | 627000000 | NULL      |
>   NULL | NULL | NULL     | qam_256    | NULL      | NULL         | NULL
>         | NULL           |       0 | NULL          | NULL      | NULL
>  | atsc       |             33 | 2006-02-16 19:27:07 |
> |       2 |        2 |          46 |         1 | 651000000 | NULL      |
>   NULL | NULL | NULL     | qam_256    | NULL      | NULL         | NULL
>         | NULL           |       0 | NULL          | NULL      | NULL
>  | atsc       |             33 | 2006-02-16 19:27:13 |
> |       3 |        2 |          62 |         1 | 687000000 | NULL      |
>   NULL | NULL | NULL     | qam_256    | NULL      | NULL         | NULL
>         | NULL           |       0 | NULL          | NULL      | NULL
>  | atsc       |             33 | 2006-02-16 19:27:19 |
> |       4 |        2 |          56 |         1 | 717000000 | NULL      |
>   NULL | NULL | NULL     | qam_256    | NULL      | NULL         | NULL
>         | NULL           |       0 | NULL          | NULL      | NULL
>  | atsc       |             33 | 2006-02-16 19:27:23 |
> +---------+----------+-------------+-----------+-----------+-----------+------------+------+----------+------------+-----------+--------------+-------------------+----------------+---------+---------------+-----------+--------------+------------+----------------+---------------------+
> 4 rows in set (0.00 sec)
>
> there is no mlpexid = 32767.  Why is that, and what is the recommended fix -
> just update tables or.... something less manual?
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
>


More information about the mythtv-users mailing list