[mythtv-commits] Ticket #10900: recording fails with "TVRecEvent dtvmultiplex.cpp:323 (ParseTuningParams) DTVMux: ParseTuningParams -- Unknown tuner type" with CableCard activated in HDHomerun Prime

[MythTV]

#10900: recording fails with "TVRecEvent dtvmultiplex.cpp:323 (ParseTuningParams)
DTVMux: ParseTuningParams -- Unknown tuner type" with CableCard activated
in HDHomerun Prime
----------------------------------+----------------------------
 Reporter:  dlbulk-mythtv@…       |          Owner:  danielk
     Type:  Bug Report - General  |         Status:  new
 Priority:  minor                 |      Milestone:  unknown
Component:  MythTV - Recording    |        Version:  0.25-fixes
 Severity:  medium                |     Resolution:
 Keywords:                        |  Ticket locked:  0
----------------------------------+----------------------------

Comment (by dlbulk-mythtv@…):

 Hi, I would like to help out and debug this problem using my setup.

 I think the problem is due to the presence of multiple card types in my
 system and they share the same source from schedules direct. Here are the
 relevant parts:

 card0: pcie, clear qam only, source1 (digital cable)
 card1: firewire, fw set-top box, source1
 card2: hdhr, cablecard, source1


 Since they share the same source, they have exactly the same set of
 channels.

 Tuning works on both clear qam and firewire, but errors on 'unknown tuner
 type' on card2.

 I am not familiar with mythtv internals. I sorta understand how the clear
 qam card tunes a channel.
 Here is one entry in my channel table:

 {{{
 mysql> select chanid,
 channum,freqid,sourceid,callsign,xmltvid,tvformat,mplexid,serviceid,atsc_major_chan,atsc_minor_chan
 from channel where callsign = "KGODT" order by channum ;
 +--------+---------+--------+----------+----------+---------+----------+---------+-----------+-----------------+-----------------+
 | chanid | channum | freqid | sourceid | callsign | xmltvid | tvformat |
 mplexid | serviceid | atsc_major_chan | atsc_minor_chan |
 +--------+---------+--------+----------+----------+---------+----------+---------+-----------+-----------------+-----------------+
 |   2071 | 7.1     | 7      |        2 | KGODT    | 19574   | ATSC     |
 141 |         3 |               7 |               1 |
 |   1707 | 707     | 707    |        1 | KGODT    | 19574   | Default  |
 57 |         1 |             707 |               0 |
 +--------+---------+--------+----------+----------+---------+----------+---------+-----------+-----------------+-----------------+
 2 rows in set (0.00 sec)
 }}}


 To tune card0 to channel 707, we lookup mplexid 57 from the dtv_mplexid
 table. Here is the entry:

 {{{
 mysql> select mplexid, sourceid, frequency, modulation, sistandard from
 dtv_multiplex where mplexid = 141 OR mplexid = 57;
 +---------+----------+-----------+------------+------------+
 | mplexid | sourceid | frequency | modulation | sistandard |
 +---------+----------+-----------+------------+------------+
 |      57 |        1 | 567000000 | qam_256    | atsc       |
 |     141 |        2 | 177000000 | 8vsb       | atsc       |
 +---------+----------+-----------+------------+------------+
 2 rows in set (0.00 sec)
 }}}


 so card0 needs to tune to frequency 567000000.

 How does this scheme work for HDHR? it is not supposed to use the
 dtv_mplex table, is it?

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/10900#comment:5>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center