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

[Klaas de Waal]

On Sat, 4 Apr 2020 at 13:40, John Pilkington <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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20200404/cc852978/attachment.htm>