[mythtv-users] Unexpected DVB-T tuning failure in master

[Klaas de Waal]

On Sat, 4 Apr 2020 at 19:55, John Pilkington <johnpilk222 at gmail.com> wrote:

> On 04/04/2020 14:01, Klaas de Waal wrote:
> >
> >
> > On Sat, 4 Apr 2020 at 13:40, John Pilkington <johnpilk222 at gmail.com
> > <mailto:johnpilk222 at gmail.com>> wrote:
> >
> >     A lot of work was done on DVB-T channel scanning recently and I
> thought
> >     it was working well, but today I tried a quick scan to see if there
> had
> >     been any changes in the local channel lineup.  All appeared to go
> well,
> >     but then scheduled recordings failed.  I don't have useful logs
> because
> >     I wasn't expecting problems.
> >
> >     I had followed my usual 'all known transports' route, which is quick
> >     and
> >     used to work for me with a system that uses only SD transmissions
> >     from a
> >     single main-chain mast.
> >
> >     On finding the problem I did a 'full scan,' which had been the focus
> of
> >     the recent changes, and recording is working again.   That scan took
> >     about 15 minutes.
> >
> >     This was with current master, 50c2d63.  I'm not sure about the
> history
> >     of the pre-existing setup, or whether v31 is likely to behave in the
> >     same way.
> >
> >
> > The v31/fixes is identical to master for channel scanning. For DVB-T/T2
> > the "Full Scan" is at the moment the recommended way of scanning because
> > this will also find transports that have moved to other frequencies. The
> > "Scan of existing transports" does not necessarily finds everything,
> > depending on what is in the NIT.
> > For everybody who is having problems with channel scanning please
> > capture the output of "mythtv-setup -v chanscan" and report it. These
> > files can become quite big so it can be a good idea to create a ticket
> > because tickets allow much larger attachments.
> >
> > Klaas.
>
> Hi Klaas:  I just repeated the sequence with the same result.  I have
> the full logs if you want them (~900 KiB), but these look likely to be
> the useful bits, from just before the output of the final channel list.
> It looks as if the recorder may not like some of the 'helpful' info that
> I suppose I must have entered sometime earlier.  System is recording, so
> I don't want to look at the transport editor now.  Is there more than
> one copy of this data?
>
> Starting from the results of a full scan, perform 'all known transports'
> scan.  After that the recorder gets no lock.
> {{{
>
> Transport list (updated) (6):
> 538000000 qam_64 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T
> rolloff:0.35 onid:9018 tsid:12294 ss:70
> 554000000 qam_64 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T
> rolloff:0.35 onid:9018 tsid:24640 ss:70
> 562000000 qam_64 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T
> rolloff:0.35 onid:9018 tsid:4166 ss:72
> 578000000 qam_64 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T
> rolloff:0.35 onid:9018 tsid:8200 ss:71
> 602000000 qam_64 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T
> rolloff:0.35 onid:9018 tsid:20544 ss:69
> 634000000 qpsk 0 auto auto 8 a 1/32 n v fec:auto msys:DVB-T
> rolloff:0.35 onid:9018 tsid:32780 ss:49
>
> }}}
>
> After another 'full scan', recording works.
> {{{
>
> Transport list (updated) (6):
> 538000000 auto 0 auto auto 8 a 1/32 n v fec:auto msys:UNDEFINED
> rolloff:0.35 onid:9018 tsid:12294 ss:70
> 554000000 auto 0 auto auto 8 a 1/32 n v fec:auto msys:UNDEFINED
> rolloff:0.35 onid:9018 tsid:24640 ss:70
> 562000000 auto 0 auto auto 8 a 1/32 n v fec:auto msys:UNDEFINED
> rolloff:0.35 onid:9018 tsid:4166 ss:72
> 578000000 auto 0 auto auto 8 a 1/32 n v fec:auto msys:UNDEFINED
> rolloff:0.35 onid:9018 tsid:8200 ss:71
> 602000000 auto 0 auto auto 8 a 1/32 n v fec:auto msys:UNDEFINED
> rolloff:0.35 onid:9018 tsid:20544 ss:69
> 634000000 auto 0 auto auto 8 a 1/32 n v fec:auto msys:UNDEFINED
> rolloff:0.35 onid:9018 tsid:32780 ss:47
>
> }}}
>
>
> Hi John,

I cannot reproduce this at the moment. Please send the full mythtv-setup
logs, created with the "-v chanscan" commandline option.

Thanks,
Klaas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20200405/ee94c396/attachment.htm>