[mythtv-users] HDHR3 recording fails, "wrong PMT"?

[Eric Sharkey]

On Wed, Dec 3, 2014 at 10:36 AM, Michael T. Dean
<mtdean at thirdcontact.com> wrote:
> On 12/03/2014 10:30 AM, Michael T. Dean wrote:
>>
>> On 12/02/2014 01:48 PM, Eric Sharkey wrote:
>>>
>>> On Mon, Dec 1, 2014 at 12:00 AM, Hika van den Hoven  wrote:
>>>>
>>>> If I google "Wrong PMT" I get among others this:
>>>> https://code.mythtv.org/trac/ticket/9976 from three years ago.
>>>> You need to delete all transports and all channels and perform a full
>>>> rescan. The delete all transports is vital.....
>>>
>>> This is the info in the dtv_multiplex table?  The channel scan doesn't
>>> update this table automatically?
>>
>>
>> Delete with mythtv-setup.
>
>
> and it will delete all the appropriate information from the cross-linked
> tables.
>
> The scanner doesn't necessarily delete any broken stuff that's in place in
> your database because it doesn't know whether the channel is still a good
> channel but just not broadcasting, now.  So, if you want to clear out broken
> stuff, do that manually, then rescan.

But why was there broken stuff in the first place?  All I did was
re-do the channel scan (in mythtv-setup) and accepted all changes it
recommended (insertion of new channels, deletion of old ones).

I'd like to understand what's actually broken about the current
configuration and why newly inserted channels from the mythtv-setup
channel scan don't work.

hdhr_config scan reports:

SCANNING: 537000000 (us-irc:76, us-cable:76)
LOCK: qam256 (ss=100 snq=100 seq=100)
TSID: 0x0001
PROGRAM 3511: 11.1 WPIX-HD
PROGRAM 3752: 2.1 WCBS-HD
PROGRAM 3754: 4.1 WNBC-HD
[..]

in mythconverg I have:

mysql> select channum, freqid, callsign, tvformat, mplexid, serviceid
from channel where chanid = 3504;
+---------+--------+----------+----------+---------+-----------+
| channum | freqid | callsign | tvformat | mplexid | serviceid |
+---------+--------+----------+----------+---------+-----------+
| 504     | 76     | WNBCDT   | ATSC     |       7 |      3754 |
+---------+--------+----------+----------+---------+-----------+
mysql> select transportid, frequency, modulation, updatetimestamp from
dtv_multiplex where mplexid = 7;
+-------------+-----------+------------+---------------------+
| transportid | frequency | modulation | updatetimestamp     |
+-------------+-----------+------------+---------------------+
|        9399 | 537000000 | qam_256    | 2013-09-14 12:01:41 |
+-------------+-----------+------------+---------------------+

Is the problem that the transport id is set to 9399 when it should be
set to 1 (TSID value from hdhr_config)?

Eric