Channel Scan improvements

[Klaas de Waal]

This ticket is intended to document and track non-trivial changes to the Channel Scan of mythtv-setup.

The idea is to add patches to this ticket that can be applied to the latest master. This gives the possibility for feedback and early testing, before the changes are committed to master.

The attached patch, 20190724-keep-channum-ok-all.patch, implements the following features.

1. Add "OK All" button

After a channel scan you can get a pop-up dialog with text like this:

"Channel xxx has channel number 1 but that is already in use. Please enter a unique channel number. Default is 5."

This question is repeated for each channel with a duplicate channel number, requiring a press on the OK button for each. There is now an "OK All" button that answers OK for all channels.

2. Keep existing channel numbers with a rescan

In mythtv-setup the channel number is by default the service ID of that channel, unless there is a LCN Logical Channel Number present. The channel numbers can later be modified with the Channel Editor of mythtv-setup.
However, this leads to conflicts when the video source is scanned again.
On a rescan mythtv-setup now keeps the existing channel numbers.
Previously, the only way known to me to have user-defined channel numbers is to run a SQL script over the channel table after each scan.

3. No more channel conflicts on service ID's

A "conflicting channel" in mythtv-setup is a channel that does not have a unique channel number. It is essential to have a unique channel number for all channels in a video source otherwise mythbackend can arbitrarily select any channel with the same channel number for a recording.
However, mythtv-setup also considers a channel conflicting if the service ID is the same as another channel and then forces the user to enter a unique channel number.
In my understanding this is a bug because A. it does not change the service ID and B. service ID's do not need to be unique.
For DVB the test on service ID is removed and all DVB channels are now considered "non-conflicting" to start with. Note that later on the check on uniqueness of the channel number is still done.

The test case for this is the Hotbird 13.0E satellite. This satellite has a number of different networks. Each network has probably unique service ID's but, over all channels of the satellite, there are many channels with identical service ID's and identical Logical Channel Numbers.
With this patch, mythtv-setup can now scan all channels of the Hotbird 13.0E with a minimum number of key presses by the user.

[Klaas de Waal]

Keep channel numbers after resecan; added "OK All" button; remove check on service ID

[Klaas de Waal <kdewaal@…>]

In 85314f4e9/mythtv:

Channel Scan improvements

Add the following features:

1. Add "OK All" button for automatic assignment of non-conflicting channel numbers.
2. Keep existing channel numbers with a rescan.
3. Allow duplicate service ID's in a single video source.

For a complete description please see ticket 13472.

Refs #13472

[Klaas de Waal]

In mythtv commit 4636d7e4146a70195b33ba9a565f01e9ed43a521

Check video source and capture card before doing a channel scan

In mythtv-setup page Channel Editor, check that a video source is selected and that the selected video source is connected to a capture card before starting the Channel Scan dialog after pressing the Channel Scan button. Give a popup message when the checks fail.

Previously, if a video source was selected that did not have a capture card connected the Channel Scan page would automatically switch to another video source, one that did have a capture card connected, without warning.

[Klaas de Waal <kdewaal@…>]

In 1c8a75d3d/mythtv:

Full search for old channels

In mythtv-setup page Channel Scan there is now a new
option "Full search for old channels".

If set, compare all channels in the database with the channels found in
the scan; otherwise only the channels in the same transport are compared.
This option is useful when you want to keep channel data such as
the xmltvid and the icon path when doing a rescan
after channels have been rearranged across transports.

For ATSC the comparison is done only on the major and minor numbers.
For DVB the comparison of channels in the same transport is done
on service id but the comparison of channels in different transports
is done on network id and service id.

Without this option, when channels have moved to another transport
the old channels are classified as "off-air" and can only be deleted.
The moved channels are classified as "New" and they then do not have
the non-scanned data anymore such as the xmltvid and the icon path
that may have been added to the old channel.

The option is currently unchecked by default. If this option proves to
be a succes then this can be changed to checked by default.

Refs #13472

[jpilk]

Minor observation. I just rescanned my single-transmitter UK Freeview DVB-T-only system to see if anything had changed. It went very smoothly, (not) finding 1 off-air channel, but reported 7 transports while listing only 6 distinct frequencies. On repeat, it found no changed channels and 6 transports.

Scan params:  All types, Unencrypted only, LCN required, Complete data, Full Search
              All known transports, ignore timeout, follow links


MythTV Version : v31-Pre-477ddfdaf5b
MythTV Branch : HEAD -> master

.....
2019-09-04 11:31:56.160298 I  CardUtil[1]: Set delivery system: DVB-T

Off-air channels (1):
qam_64:538000000:Loveworld:270:15000:0: 10270:cnt(pnum:1,channum:1)

2019-09-04 11:32:47.134756 I  ChanImport: Old channels found in same transport: 134
2019-09-04 11:32:47.134766 I  ChanImport: Old channels found in other transport: 0
2019-09-04 11:32:47.134773 I  ChanImport: Old channels not found (off-air): 1

Channel list (134):
qpsk:514000000:Notts TV:7:12323:9018:32844:32780=32780:dvb      10007:cnt(pnum:1,channum:1)
....
qam_64:762000000:QVC Beauty:35:12323:9018:28288:24640=24640:dvb 10035:cnt(pnum:1,channum:1)

Found 7 transports:
Channels: FTA Enc Dec
ATSC        0   0   0
DVB       134   0   0
SCTE        0   0   0
MPEG        0   0   0
NTSC        0
Unique: prog 134 atsc 0 atsc minor 0 channum 134
Max atsc major count: 0

=========
(rescan)
....
qam_64:762000000:QVC Beauty:35:12323:9018:28288:24640=24640:dvb 10035:cnt(pnum:1,channum:1)

Found 6 transports:
Channels: FTA Enc Dec
ATSC        0   0   0
DVB       134   0   0
SCTE        0   0   0
MPEG        0   0   0
NTSC        0
Unique: prog 134 atsc 0 atsc minor 0 channum 134
Max atsc major count: 0

....
qam_64:762000000:QVC Beauty:35:12323:9018:28288:24640=24640:dvb

2019-09-04 11:43:41.151328 I  ChanImport: Found 0 unused transports.
2019-09-04 11:44:03.451605 I  OpenGL2: Deleting OpenGL Resources
2019-09-04 11:44:03.452743 I  OpenGL: Deleting OpenGL Resources
[john@HP_Box ~]$

[Klaas de Waal]

Questions:

• Did you delete the off-air channels at the end of the first scan?
• Is the 538MHz present in the channel list of the first scan?
• Is the list of 134 channels found in the first scan identical to the 134 channels found in the second scan?

If you still have the complete log then maybe you can add it to the ticket?

N.B. I do appreciate you giving the values of the scan parameters.

[jpilk]

IIRC I accepted the changes from the first scan and exited mythtv-setup. Then re-entered and scanned again, same params. The frequencies listed were the same in each run, and are those known to the Transport Editor. I think the channel list was unchanged by the second scan, but I didn't check it in detail. No changes were reported. I'm afraid I didn't save the log, and rebooted afterwards, so it has gone.

As you can see from the timestamps it was all quite quick. Obviously I can't create new channels for testing but I will save logs the next time I see anything noteworthy. And thanks!

[jpilk]

Tuning log of DVB-T/T2 system

[jpilk]

Log attached from MyGica? 230 tuner under 5.2.11-100.fc29.x86_64 File setup4.log

The DVB-T tuner is having trouble with 2 transports and its logs have ended unexpectedly. Perhaps the rain problem again. The teed displayed logs ended with 'Handling Aborted'. File setup.log

It's also just conceivable that the unexpected exit was caused by a current kdeinit5 closure bug in F29.

[jpilk]

Successful scan of DVB-T transports: setup5.log

[Klaas de Waal <kdewaal@…>]

In 796c4c582/mythtv:

No more channel conflicts on ATSC major/minor numbers.

This change is similar to that for channel conflicts on service ID's for DVB.

Rationale (also the same):
A "conflicting channel" in mythtv-setup is a channel that does not have a unique channel number.
It is essential to have a unique channel number for all channels in a video source otherwise
mythbackend can arbitrarily select any channel with the same channel number for a recording.
However, mythtv-setup also considers a channel conflicting if the ATSC major/minor number
combination is the same as another channel and then forces the user to enter a unique channel number.

In my understanding this is a bug because A. it does not change the ATSC major/minor numbers
and B. ATSC major/minor number combinations do not need to be unique in MythTV.
For ATSC the test on the major/minor number combination uniqueness is removed and all ATSC channels
are now considered "non-conflicting" to start with.
The ATSC major/minor number combination is used to create default channel numbers
but later on the check on the uniqueness of the channel number is still done.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In 6ab6329ce1/mythtv:

Number of transports in mythtv-setup log output

The number of transports in the summary of the log output
is now always the number of transports found in the scan.
In the processing of the scan results, at some point all
transports of channels in the database that are not found in the scan,
called the off-air channels, are added to the list of transports.
This caused an incorrect number of transports to be presented.
This is now fixed.
Also added a summary of the scan parameters in the log output.
Also added, when option -v chanscan is given, a separate
listing of all transports found, in order of ascending frequency.

Refs #13472

[jpilk]

Scan of all known transports for DVB-T only and DVB-T/T2 tuners at 2dcfeb4

[jpilk]

This scan was the second tried after the build, and looks OK. The first one, with wind and rain, again had problems with one DVB-T transport and included 26 lines of CVCT debug info at the start of the DVB-T/T2 section; but those results looked OK too.

[Klaas de Waal <kdewaal@…>]

In be306250bd/mythtv:

Suggested channel number in case of conflicts

When there are after a channel scan duplicate channel numbers
a suggested channel number is presented to the user.
The algorithm to create this number is now slightly changed.
For ATSC the algorithm is not changed.
For DVB the sequence is now:

• Try the existing channel number
• Try the service ID
• If there is a Frequency ID (channel) try frequency ID - service ID
• Try Service ID - Network ID
• Try Service ID - Transport ID
• Find an unused channel number.

This has the following advantages:

• Duplicate channels are now in the Channel Editor sorting adjacent

to the original channel. This makes it easy to select which one to keep.

• The unused channel numbers are kept unused as long as possible;

allocating a channel to an unused channel number can cause another
duplicate later in the scanning process.
Note that this problem happens in practice only when scanning
satellites; usually the service ID, which is used as channel number
when there is no Logical Channel Number available, is unique.

Refs #13472

[Klaas de Waal <klaas@…>]

In 952e76461c/mythtv:

Show transport ID and frequency in Channel Options editor

In mythtv-setup, show the transport stream ID and the frequency of the
transport stream in the Channel Editor, page "Channel Options - Common".
Add and extend some help texts in this page.
The transport stream ID or the frequency is needed to find
the transport stream of a channel in the "Edit Transports" page.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In d7a79b6a5/mythtv:

Mythtv-setup option "Complete scan data required"

Check for all channels the PAT/PMT consistency.
Check only for non-ATSC channels the PAT/PMT/SDT consistency.
This solves the problem that selecting this option caused
all ATSC channels to be filtered out.
This option is now selected by default again.
This reverts commit 1c0d46a.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In f9eadcacf5/mythtv:

Increase default tuning timeout values

For DVB-T/T2/C devices, increase the default signal timeout values from 1000ms
to 3000ms and the default tuning timeout values from 3000ms to 6000ms.
For ATSC devices, increase the default signal timeout value from 500ms to
2000ms and the default tuning timeout value from 2000ms to 4000ms.
This does increase the chance of getting good signal especially on DVB-T/T2.
This does increase the channel scanning time when there is no signal
on the frequency that is tuned to, which happens when doing a "Full Scan"
in which a list of frequencies is tried just to see if there
is something present there.
Note that this are the default values for new capture cards.
The timeout values of existing capture cards is not changed.
It is always possible to change the timeout values in the Capture Card settings page.

Refs #13472

[Klaas de Waal]

In commit ef9cc022c1baa888add8b4d0bfc99ec190b0c607 (but not mentioned in the commit comments):

Logical channel numbers maybe possible on all Sky satellite channels.

The way the channel numbers are coded on the Astra-2 28E2 satellite for Sky UK is done in exactly the same way on the Sky New Zealand satellite. It uses the same private descriptor so table 0xB1 with the channel numbers should be decoded correctly. For New Zealand, the orginal network ID is different and the bouquet ID is specific for New Zealand and most likely also region-specific.

I have now removed the check on the original network ID so that a channel scan with mythtv-setup might now get the channel numbers correct for all Sky satellites if they use this way of channel number coding everywhere.

Note that there must be a valid bouquet ID given in the Video Source; this is needed to select the bouquet that contains the channel numbers.

[Mark Spieth <mspieth@…>]

In efbc436e3/mythtv:

OpenTV logical channel numbers

Support for OpenTV logical channel numbers as used
by Sky (US/IT/NZ/AU), Dishnet(US) and others.
The Bouquet ID and the Region ID, needed to get the correct
tables, can be defined in the video source similar to how it
is done for the Freesat and Sky UK channel numbers.
Scanning is activated by a new "Scan OpenTV" channel scanning option.
As a next step, when the applicable network ID's and private descriptor
identifiers are known, the identification of a stream with OpenTV
channel numbers can be done automatically.

Refs #13472
Fixes #13547

Signed-off-by: Klaas de Waal <klaas@…>

[Klaas de Waal <klaas@…>]

In 83d8bbc825/mythtv:

Fallback for modulation system setting with DVB-T/T2 and DVB-S/S2

The checks on the correct modulation system setting in dvt_multiplex is
now more relaxed; if there is no value defined then a suitable default is chosen.
This eases migration from old mythtv installations to v31.
Also changed default selection to DVB-T2 and DVB-S2 in popup menu's.

Refs #13472
Refs #12638

[Klaas de Waal <kdewaal@…>]

In 6d2e7b2771/mythtv:

Use channel frequency table defaults for ATSC channel scanning

Use the Channel frequency table value defined in the Video source or,
when that is "default", the frequency table value defined in the
General / Locale settings as default for the ATSC scan type "Full Scan"
frequency table parameter in the Channel Scan page.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In aeb0f2558/mythtv:

Use channel frequency table defaults for ATSC channel scanning

Use the Channel frequency table value defined in the Video source or,
when that is "default", the frequency table value defined in the
General / Locale settings as default for the ATSC scan type "Full Scan"
frequency table parameter in the Channel Scan page.

Refs #13472

(cherry picked from commit 6d2e7b2771cc520389222ce4a94503ee20e885c7)
Signed-off-by: Klaas de Waal <klaas@…>

[Klaas de Waal <kdewaal@…>]

In 3c6622881e/mythtv:

Always listen to ATSC_PSIP_PID with Channel Scanning

Sometimes the Channel Scanner does not listen anymore
to the ATSC_PSIP_PID after a stream reset.
In that case a timeout occurs and no channels are found.
This is fixed by always calling ScanStreamData::Reset when
a stream is reset during channel scanning.

Refs #13472

[Klaas de Waal]

In commit f1ea02d40b52d2a46636159c659c45d061bcf1d2

One-part channel number for ATSC cable

Implement the one-part channel number for ATSC cable as defined in ATSC standard A65/2013 7 August 2013 page 35. In this case the ATSC major number is 1008 (0x3F0) or higher and all channels in all multiplexes have this major number.

Change the name of the MPTS full-transport stream channel to use the freqid instead of the major number when the one-part channel number is used.

[Klaas de Waal]

In commit cae6477880ce310a4b43516eb8fde73c9b06754e

ATSC scan fixes part 1

Fix HasCachedAllCVCTs and HasCachedAllTVCTs to give the correct answer when no tables have been found yet. Add listening to SCTE_PSIP_PID in the stream reset functions because this pid is also added in the constructor.

[Klaas de Waal <kdewaal@…>]

In b4fc0e1f8a/mythtv:

SDT Service Description Table in ATSC cable

SDT tables can also be found in ATSC ClearQAM cable signals.
Previously the presence of a SDT caused the transport to be
identified as DVB.
The following problems have been fixed:

• Channels classified as "dvb" instead of "atsc". A channel is now "atsc" if there is an MGT Master Guide Table.
• Timeout waiting for the NIT Network Information Table. If there is an MGT we do not wait for the NIT and the SDT.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In 3c6622881e/mythtv:

Always listen to ATSC_PSIP_PID with Channel Scanning

Sometimes the Channel Scanner does not listen anymore
to the ATSC_PSIP_PID after a stream reset.
In that case a timeout occurs and no channels are found.
This is fixed by always calling ScanStreamData::Reset when
a stream is reset during channel scanning.

Refs #13472

[Klaas de Waal]

Transport Editor for DVB-C

The transport editor of mythtv-setup can now edit the modulation system of a DVB-C transport stream multiplex to any of the three supported values. The list of choices and the default value for the symbol rate are now correct for DVB-C and the same as presented in the "Full Scan (Tuned)" pane of the scanner.

Commit: afb2de9fa4418a23a0e4fc2bac65d54ede58a83f

[Klaas de Waal <kdewaal@…>]

In ac67d5837/mythtv:

Wait for NIT or MGT when scanning

In mythtv-setup channel scan, wait for a NIT or a MGT when the
PAT/PMT have been found. This solves the problem that sometimes
channels are found but the channel names are missing.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In c7128cf0d3/mythtv:

SDT Service Description Table in ATSC cable

SDT tables can also be found in ATSC ClearQAM cable signals.
Previously the presence of a SDT caused the transport to be
identified as DVB.
The following problems have been fixed:

• Channels classified as "dvb" instead of "atsc". A channel is now "atsc" if there is an MGT Master Guide Table.
• Timeout waiting for the NIT Network Information Table. If there is an MGT we do not wait for the NIT and the SDT.

Refs #13472

(cherry picked from commit b4fc0e1f8a4fd617bfd9ab4663ae58005a3882db)
Signed-off-by: Klaas de Waal <kdewaal@…>

[Klaas de Waal <kdewaal@…>]

In 7097da34c/mythtv:

Always listen to ATSC_PSIP_PID with Channel Scanning

Sometimes the Channel Scanner does not listen anymore
to the ATSC_PSIP_PID after a stream reset.
In that case a timeout occurs and no channels are found.
This is fixed by always calling ScanStreamData::Reset when
a stream is reset during channel scanning.

Refs #13472

(cherry picked from commit 3c6622881e746413733a8ff3bfa4e37068e21624)
Signed-off-by: Klaas de Waal <kdewaal@…>

[Klaas de Waal <kdewaal@…>]

In 405e049c7/mythtv:

Duplicate channel number

In a channel scan, channels with duplicate channel numbers now
get a suffix A, B etc to make them unique.
In DVB the broadcasters can define logical channel numbers;
this are usuallly numbers from 1 upwards.
In ATSC a channel number can be a major/minor number, e.g. 7_2.
An ATSC channel number can also be defined by the broadcaster
as a single number from 1 upwards, similar to DVB.
If there is nothing defined then the service ID of the channel
is used as channel number. A service ID is generally unique
within a network but especially on satellites it can happen that
thereare different channels with the same service id.
When receiving OTA signals via aerials/antenna's it can happen
that the same multiplex is received from different transmitters.
This will also lead to duplicate channel numbers.
It is now easier to recognize duplicate channels because they
are shown next to each other in the program guide and in
the mythtv-setup channel editor.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In f599c35bd/mythtv:

Duplicate channel number

In a channel scan, channels with duplicate channel numbers now
get a suffix A, B etc to make them unique.
In DVB the broadcasters can define logical channel numbers;
this are usuallly numbers from 1 upwards.
In ATSC a channel number can be a major/minor number, e.g. 7_2.
An ATSC channel number can also be defined by the broadcaster
as a single number from 1 upwards, similar to DVB.
If there is nothing defined then the service ID of the channel
is used as channel number. A service ID is generally unique
within a network but especially on satellites it can happen that
thereare different channels with the same service id.
When receiving OTA signals via aerials/antenna's it can happen
that the same multiplex is received from different transmitters.
This will also lead to duplicate channel numbers.
It is now easier to recognize duplicate channels because they
are shown next to each other in the program guide and in
the mythtv-setup channel editor.

Refs #13472

(cherry picked from commit 405e049c761135fd27c9def46137809144e6f2e9)
Signed-off-by: Klaas de Waal <kdewaal@…>

[Klaas de Waal <kdewaal@…>]

In 31129946b7/mythtv:

Signal strength of scanned transports

Show the signal strength of the scanned transports in the transport list.
The transport list is shown if the "-v chanscan" option is given when running mythtv-setup.
The signal strengths are useful to determine which transport to choose when identical
transports can be received from different transmitters on different frequencies.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In d0626e9028/mythtv:

Scan option "Remove duplicate channels"

Add new scan option to remove duplicate transports and duplicate
channels based on signal strength of the received signal.
This can be useful when receiving DVB-T2 and other OTA signals
when the same channels can sometimes be received from more than
one transmitter on different frequencies.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In 1b4d44b46/mythtv:

Updated "Remove duplicates" channel scan option

Renamed the feature from "Remove duplicate channels" to "Remove duplicates".
Changed the default for this option to Selected/Checked?.
Removed the check on individual channels across all scanned channels.
The implementation does not check for original network ID plus transport ID
on a per-transport basis, as suggested in ticket #12107 for DVB, but it checks
this on all channels in the transport. The implementation is also expected to work for ATSC.
Thanks to John Pilkington for numerous tests in the daily changing UK Freeview landscape.

Refs #13472
Fixes #12107

[Klaas de Waal <kdewaal@…>]

In 81d4056c2/mythtv:

Wait for NIT or MGT when scanning

In mythtv-setup channel scan, wait for a NIT or a MGT when the
PAT/PMT have been found. This solves the problem that sometimes
channels are found but the channel names are missing.

Refs #13472

(cherry picked from commit ac67d5837062ab47aa6f9b93df001a2a245d32ad)
Signed-off-by: Klaas de Waal <kdewaal@…>

[Klaas de Waal <kdewaal@…>]

In d052cbc41c/mythtv:

Signal strength of scanned transports

Show the signal strength of the scanned transports in the transport list.
The transport list is shown if the "-v chanscan" option is given when running mythtv-setup.
The signal strengths are useful to determine which transport to choose when identical
transports can be received from different transmitters on different frequencies.

Refs #13472

(cherry picked from commit 31129946b719ff21b1a6cad86b2580ef8043a10f)
Signed-off-by: Klaas de Waal <kdewaal@…>

[Klaas de Waal <kdewaal@…>]

In e0e09b6b6/mythtv:

Scan option "Remove duplicate channels"

Add new scan option to remove duplicate transports and duplicate
channels based on signal strength of the received signal.
This can be useful when receiving DVB-T2 and other OTA signals
when the same channels can sometimes be received from more than
one transmitter on different frequencies.

Refs #13472

(cherry picked from commit d0626e90287427408b28e2b0eabe12c0cb835118)
Signed-off-by: Klaas de Waal <kdewaal@…>

[Klaas de Waal <kdewaal@…>]

In c8c59f554/mythtv:

Updated "Remove duplicates" channel scan option

Renamed the feature from "Remove duplicate channels" to "Remove duplicates".
Changed the default for this option to Selected/Checked?.
Removed the check on individual channels across all scanned channels.
The implementation does not check for original network ID plus transport ID
on a per-transport basis, as suggested in ticket #12107 for DVB, but it checks
this on all channels in the transport. The implementation is also expected to work for ATSC.
Thanks to John Pilkington for numerous tests in the daily changing UK Freeview landscape.

Refs #13472
Fixes #12107

(cherry picked from commit 1b4d44b468de0a8c7ad2c25a1d779ce1dc2c06b8)
Signed-off-by: Klaas de Waal <kdewaal@…>

[Klaas de Waal <kdewaal@…>]

In ee78ba330/mythtv:

Simplify channel numbering

Simplify the channel numbering scheme to the following:

• Use the Logical Channel Number
• If that is not present then:
  • For ATSC, use the Major-Minor channel number
  • For DVB and everything else, use the service ID

If this results in a duplicate, a channel number that is
already present in the video source, then the channel number
gets a suffix A, B, or C etc to make it unique.
The advantage of this is that a channel has a more
predictable location in the program guide.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In 82502230c0/mythtv:

Hide invisile channels in Channel Editor

In the Channel Editor, when the option "Hide Channels without channel number."
is selected, the invisible channels are now also hidden.
This is convenient when editing channels in a video source where
many channels are set invisible.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In 0085bdf66/mythtv:

Update transports with NIT delivery system descriptors

When the list of transports is extended with information found
in the delivery system descriptors in the NIT then do the scan
always with that information.
Previously, when there was already a transport at the frequency
specified in the NIT then the information in the NIT was
discarded and the old information in the transport was used.
This causes problems when the existing information is not correct.

Refs #13472

[Klaas de Waal <kdewaal@…>]

In c970d5837/mythtv:

Fix "Import Existing Scan" option

Fix the Channel Scan option "Import Existing Scan".
This option has been broken since adding the field service_type
to database table channel in ticket #8774.
The functionality has been restored, but excluding the service_type value which
will be added before release of v32 as this requires a database schema change.

Other changes are:

• Present the saved scans in descending chronological order, so with the newest on top
• When saving a new scan, delete all scans older than 14 days from that video source Previously, only scans created with the same capture card were deleted.
• Delete al saved scans of a video source when the video source is deleted

Refs #8774
Refs #13472

[Klaas de Waal <kdewaal@…>]

In e05a8a841b/mythtv:

Discard PAT for wrong multiplex

When waiting for the PAT for a specific transport stream multiplex
discard PATs for other multiplexes.
After a new tuning request there can be still a number of packets received
from the previous multiplex and these packets can contain a PAT.
This fixes incorrect "Program not found in PAT" and "Rescan your transports"
messages that can sometimes be seen even immediately after a succesful scan.

Refs #13472

[Klaas de Waal <klaas@…>]

In f1cfc489b0/mythtv:

Support DMBTH (DTMB) as DVB-T

Select tuner type DVB-T when the card supports modulation system DMBTH (DTMB).
This restore the behavior of MythTV v30 that was lost in v31.

Refs #13472

(cherry picked from commit 2e1cccb628f92091641657f67f25852c746a7887)
Signed-off-by: Klaas de Waal <kdewaal@…>

[Klaas de Waal]

No big changes in channel scanning foreseen for the near future, but when that happens new tickets will be created as Github issues. Therefore closing this ticket.

[Klaas de Waal <klaas@…>]

In 2e1cccb62/mythtv:

Support DMBTH (DTMB) as DVB-T

Select tuner type DVB-T when the card supports modulation system DMBTH (DTMB).
This restore the behavior of MythTV v30 that was lost in v31.

Refs #13472