Skip to content

Commit

Permalink
Do not use exsting multiplex tuning data in a Full Scan
Browse files Browse the repository at this point in the history
In a Full Scan the list of frequencies to be scanned and
the tuning parameters are generated from tables.
Previously, the tuning parameters were overwritten by the values
in the database if there was already a multiplex with that
frequency present in the database.
The problem with this was that if the information in the database
was not correct then that frequency could never be tuned again
unless the multiplex was deleted with the Transport Editor or
when a new video source, without multiplexes,  was created.
  • Loading branch information
kmdewaal committed Apr 12, 2020
1 parent 541f883 commit 52bde49
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion mythtv/libs/libmythtv/frequencytables.cpp
Expand Up @@ -122,7 +122,8 @@ TransportScanItem::TransportScanItem(uint sourceid,
m_tuning.m_fec = ft.m_fecInner;
}

m_mplexid = GetMultiplexIdFromDB();
// Do not use tuning information from database for the "Full Scan"
// m_mplexid = GetMultiplexIdFromDB();
}

TransportScanItem::TransportScanItem(uint _sourceid,
Expand Down

0 comments on commit 52bde49

Please sign in to comment.