[mythtv-users] Suddenly only recording in SD, not HD

[Andy Smith]

On 28/04/2023 23:37, John Pilkington wrote:
> On 28/04/2023 23:03, John Pilkington wrote:
>> On 28/04/2023 21:40, Andy Smith wrote:
>>>
>>> On 28/04/2023 17:27, Karl Buckland wrote:
>
>>>
>> I have rescanned with nothing similar.  But
>>
>> https://www.freeview.co.uk/help/service-updates/channel-changes-26-April-2023 
>>
>
> In fact I saw the equivqlent change earlier this month.  The HD 
> Transport ID changed from 16517 to 16518
>
> Waltham, East Midlands
>
> Nov 2022
> Transport list before processing (7):
> 538000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:12294 ss:58
> 554000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:24640 ss:57
> 562000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:4166 ss:61
> 578000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:8200 ss:60
> 586000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T2 ro:0.35 
> onid:9018 tsid:16517 ss:62    *******
> 602000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:20544 ss:58
> 634000000 qpsk a 0 3/4 1/2 8 8 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:32780 ss:36
>
> Today
> Updated old transports (7):
> 538000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:12294 ss:65
> 554000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:24640 ss:64
> 562000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:4166 ss:67
> 578000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:8200 ss:65
> 586000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T2 ro:0.35 
> onid:9018 tsid:16518 ss:67   *******
> 602000000 auto 0 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:20544 ss:62
> 634000000 qpsk a 0 3/4 1/2 8 8 1/32 n v fec:auto msys:DVB-T ro:0.35 
> onid:9018 tsid:32780 ss:41
>
>>
>> John P

Hi John,

Thanks for the tip, I assumed that because the scan of that transport 
found all the expected channels, the transport itself must have been 
correctly configured.  I looked in the channelscan_channel table and 
sure enough, the HD Transport ID has changed from 16515 to 16524 but 
this has not been updated in the dtv_multiplex table.

mysql> SELECT `scanid`, `mplex_id`, `service_name`, `chan_num`, 
`service_id`, `sdt_tsid` FROM `channelscan_channel` WHERE `scanid` = 
'34' AND `mplex_id` = '7' AND `sdt_tsid` > '0';

+--------+----------+---------------+----------+------------+----------+
| scanid | mplex_id | service_name  | chan_num | service_id | sdt_tsid |
+--------+----------+---------------+----------+------------+----------+
|     34 |        7 | BBC TWO HD    | 102      |      17472 | 16524 |
|     34 |        7 | BBC ONE SE HD | 101      |      17548 | 16524 |
|     34 |        7 | ITV1 HD       | 103      |      17603 | 16524 |
|     34 |        7 | Channel 4 HD  | 104      |      17664 | 16524 |
|     34 |        7 | Channel 5 HD  | 105      |      17728 | 16524 |
|     34 |        7 | BBC THREE HD  | 109      |      17920 | 16524 |
|     34 |        7 | BBC FOUR HD   | 106      |      18048 | 16524 |
|     34 |        7 | CBBC HD       | 204      |      18112 | 16524 |
|     34 |        7 | CBeebies HD   | 205      |      18176 | 16524 |
|     34 |        7 | TBN UK        | 66       |      20160 | 16524 |
|     34 |        7 | 5SELECT       | 56       |      20256 | 16524 |
+--------+----------+---------------+----------+------------+----------+
11 rows in set (0.00 sec)

mysql>

After updating the transportid for mplexid 7 in the dtv_multiplex table 
and restarting the backend, all the HD channels are working once more.

Thanks again.
-- 
Andy