[mythtv-commits] [MythTV/mythtv] 5575f4: Hz/kHz confusion in SatelliteDeliverySystemDescriptor

[rogerjames99]

  Branch: refs/heads/master
  Home:   https://github.com/MythTV/mythtv
  Commit: 5575f4f6a7bd9fc12677f2c1ac6d67685f3c557c
      https://github.com/MythTV/mythtv/commit/5575f4f6a7bd9fc12677f2c1ac6d67685f3c557c
  Author: Roger James <roger at beardandsandals.co.uk>
  Date:   2019-11-18 (Mon, 18 Nov 2019)

  Changed paths:
    M mythtv/libs/libmythtv/channelscan/channelscan_sm.cpp
    M mythtv/libs/libmythtv/channelutil.cpp
    M mythtv/libs/libmythtv/dtvmultiplex.cpp
    M mythtv/libs/libmythtv/mpeg/dvbdescriptors.cpp
    M mythtv/libs/libmythtv/mpeg/dvbdescriptors.h

  Log Message:
  -----------
  Hz/kHz confusion in SatelliteDeliverySystemDescriptor

In SatelliteDeliverySystemDescriptor the function FrequencyHz
did return the frequency in kHz. This is, although misleading,
not a real bug because almost everwhere the value was correctly
interpreted as a frequency in kHz, as is standard for all
frequencies in the context of satellites.
Only in the channel scanner, where the NIT table is parsed
for additional transports, the result of FrequencyHz was
divided by 1000 and this resulted in a value in MHz.
Contrary to what the title of ticket #13058 suggests,
this did not prevent finding and scanning new multiplexes.
The code uses the frequency value to search for an existing
multiplex and if it cannot find it then a new multiplex is created.

Fixes #13058

Signed-off-by: Klaas de Waal <kdewaal at mythtv.org>