Opened 15 years ago
Closed 15 years ago
#6756 closed defect (fixed)
DVB-S Scanning Problems
Reported by: | stuartm | Owned by: | Janne Grunau |
---|---|---|---|
Priority: | major | Milestone: | 0.22 |
Component: | MythTV - Channel Scanner | Version: | head |
Severity: | medium | Keywords: | |
Cc: | Stuart Auchterlonie | Ticket locked: | no |
Description (last modified by )
- Only scans the starting frequency and not others in the NIT with a full scan
- Inserts a dozen identical copies of the multiplex into the dtv_multiplex table
- Doesn't always insert discovered channels when 'Insert All' selected (I could only get it to insert channels for the first mplex)
- Update timestamp is not populated
Change History (15)
comment:2 Changed 15 years ago by
Insertion bug seems fairly simple - "Trying to bind a value to placeholder :NETWORKID without occurrence in the prepared query. Ignoring it."
comment:4 Changed 15 years ago by
The number of times the multiplex is inserted is determined by the number of channels. So for a multiplex with 4 channels the multiplex information is duplicated 4 times.
comment:5 Changed 15 years ago by
comment:6 Changed 15 years ago by
Priority: | critical → major |
---|---|
Severity: | high → medium |
Problems 2 and 3 are now fixed. 1 and 4 remain.
Scanning is painfully slow. Default scanning timeouts could be as much as 1/10th their current values or even eliminated entirely, a full scan could take over an hour.
comment:7 Changed 15 years ago by
As far as I recall, DVB-s scan timeouts are as they are to cope with rotors. Of course, no current user appears to have a rotor, so we don't even have confirmation that they even still work with trunk.
comment:8 Changed 15 years ago by
could the timeouts be made conditional on the presence of a rotor in the configuration of the LNB?
comment:9 Changed 15 years ago by
Cc: | Stuart Auchterlonie added |
---|
comment:10 Changed 15 years ago by
comment:11 Changed 15 years ago by
Owner: | changed from danielk to Janne Grunau |
---|---|
Status: | new → accepted |
I can't reproduce "4. Update timestamp is not populated"
comment:12 Changed 15 years ago by
(In [21362]) change data structure holding scanning information from QMap to QList<QPair>
There no real advantage of using a map over a list. In the following commits the transport_scan_items_t underlaying container will change from QList to a real double linked list. This is needed for extending the list of transports to scan during the scan since a reallocation during appending to a QList invalidates all iterators. We can't use std::list iterators as keys of the map.
Refs #6756
comment:13 Changed 15 years ago by
comment:14 Changed 15 years ago by
comment:15 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Fix spacing