Opened 17 years ago
Closed 15 years ago
#3119 closed defect (fixed)
Non-unique ATSC channel numbers confuse channel scanner
Reported by: | Owned by: | danielk | |
---|---|---|---|
Priority: | minor | Milestone: | 0.22 |
Component: | channelscan | Version: | head |
Severity: | medium | Keywords: | channel scanner QAM |
Cc: | sastie@… | Ticket locked: | no |
Description
Problem with the channel scanner in the following case: QAM 256 - Cable high IRC. All QAM channels are broadcasted with the same ATSC Major - ATSC Minor combination. (1008-0)
Result: Channel scanner picks first channel, inserts it to the db. Channel scanner picks up subsequent channels and run an update script on previously inserted channel. End up having 1 QAM channel instead of 23.
Workaround: took mysql query log file and transformed "update" queries into "insert" queries. ran the scripts to have the channels in the db.
Proposed solution: use the frequency and multiplex to isolate a channel and not just ATSC major-minor.
Change History (5)
comment:1 Changed 17 years ago by
comment:2 Changed 17 years ago by
Component: | dvb → channelscan |
---|
comment:3 Changed 17 years ago by
Summary: | Channel scanner problem when different channels have same ATSC major - ATSC minor values → Non-unique ATSC channel numbers confuse channel scanner |
---|---|
Version: | 0.20 → head |
comment:4 Changed 15 years ago by
Status: | new → assigned |
---|
comment:5 Changed 15 years ago by
Milestone: | unknown → 0.22 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
should be fixed by channelscan merge
(In [13256]) Refs #2695. Refs #2909. Refs #3119. Refs #3190. Refs #2830. Refs #2600. This commit creates a branch for working on the channel scanner.