[mythtv-users] HDTV and Myth Chan Scan

[Michael Haan]

On 2/17/06, R. G. Newbury <newbury at mandamus.org> wrote:
>
> Michael Haan 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?
> Take a look at the channel table. There must be an mplexid entry for
> channel 213 (as well as a serviceid). You will need to do:
>
> update channnel set mplexid = 'x', serviceid='y' where channum='213';
>
>
> Geoff
>
> --
>        R. Geoffrey Newbury
>      Barrister and Solicitor
> Suite 106, 150 Lakeshore Road West
>     Mississauga, Ontario, L5H 3R2
>
>   905-271-9600  Fax 905-271-1638
>        newbury at mandamus.org
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

Yeah, I'm just curious why the scan didn't do that.  From the table above,
how do I know which mplexid to set?  And where do I find the service ids?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20060217/1211a12b/attachment-0001.htm