[mythtv-users] ITV4 recordings empty: Freeview channel number duplicated.

[John Pilkington]

On 29/08/15 12:47, John Pilkington wrote:
> On 29/08/15 11:18, John Pilkington wrote:
>> On 29/08/15 09:52, John Pilkington wrote:
>>> On 29/08/15 00:07, Robert Kulagowski wrote:
>>>> On Fri, Aug 28, 2015 at 1:25 PM, John Pilkington <J.Pilk at tesco.net>
>>>> wrote:
>>>>> I've had 'empty' recordings from ITV4 and ITV3+1 in the last two days
>>>>> - and
>>>>> just saw that they were made with channel numbers 792, 793 instead of
>>>>> the
>>>>> expected 24 and 34.  A rescan this morning found all of these
>>>>> entries.  I'm
>>>>> getting a real recording now after using mythtvsetup to delete the 79*
>>>>> channels.
>>>>>
>>>>> Perhaps this is an 'interactive TV' function?  I see I have that
>>>>> disabled
>>>>> (in the Playback OSD screen)
>>>>
>>>> We've [Schedules Direct] found out from Freeview that those are
>>>> temporary and are supposed to be removed in the next week or so.
>>>
>>> Thanks; yes, that's what I expect will happen, and normal operation will
>>> return.  My TV showed a 'Please rescan' screen different from the usual
>>> internally generated one, but myth recorded as normal, even after a
>>> rescan, selecting the old mux and giving 900 MB files that didn't play.
>>>   I was puzzled.
>>>
>>> The good recording from ITV4 on channel 24 now has Myth chanid 1742 :-)
>>>
>>>  From a scan on 7 Aug:
>>>
>>> qam_64:762000000:ITV4:24:12323:9018:28032:24640=24640:dvb
>>> 1024:cnt(pnum:1,channum:1)
>>>
>>> And from scans made yesterday:  the old channel/mux seen above is now
>>> called 792.
>>>
>>> qam_64:737833000:ITV4:24:12323:9018:8330:8200=8200:dvb
>>> 0:cnt(pnum:1,channum:1)
>>>
>>> qam_64:762000000:ITV4:792:12323:9018:28032:24640=24640:dvb
>>> 1024:cnt(pnum:1,channum:1)
>>>
>>>
>>> qam_64:538000000:ITV3+1:793:12323:9018:16016:12294=12294:dvb
>>> 1034:cnt(pnum:1,channum:1)
>>>
>>> qam_64:762000000:ITV3+1:34:12323:9018:27232:24640=24640:dvb
>>> 0:cnt(pnum:1,channum:1)
>>>
>>>
>>> qam_64:762000000:CITV:122:12323:9018:27296:24640=24640:dvb
>>> 0:cnt(pnum:1,channum:1)
>>>
>>> qam_64:538000000:CITV:795:12323:9018:16032:12294=12294:dvb
>>> 1122:cnt(pnum:1,channum:1)
>>>
>>
>> It looks as if X in the X:cnt(pnum:1,channum:1) phrase is being wrongly
>> set.  the '0' should be in the old-params line, associated with the
>> obsolete 79* channel. The non-zero value in the other line is the chanid
>> that MythTV will use.  Bug in the post-scan sort?
>>
>> I see the same in my current-master-head buntu system.
>>
>
> A scan a few minutes ago now shows the old settings, 79*, as disabled
> (0) and the new values as ITV4/24/1734, ITV3+1/34/1735 and
> CITV/122/1736.  It will probably work like that... but perhaps those
> chanids will eventually revert to their usual relationship with channel
> numbers?
> Rather looks like transients at source.
>
> Over and out..,  I hope.

Not quite.  That was the result of an 'all known transports' update on 
my HD-capable current-master box.  A similar scan on the SD-only 
qt4-era-master box, with 6 active transports instead of 8, updated ITV4 
but still had the old-parameter ITV3+1 and CITV 79* channels as default. 
   Looks like a mux-updates-not-in-sync effect.  I've manually deleted 
all the 79* channels on both boxes and will hope for the best.  I rarely 
record the affected channels anyway!