Opened 14 years ago

Closed 11 years ago

#3119 closed defect (fixed)

Non-unique ATSC channel numbers confuse channel scanner

Reported by: sastie@… Owned by: danielk
Priority: minor Milestone: 0.22
Component: channelscan Version: head
Severity: medium Keywords: channel scanner QAM
Cc: sastie@… Ticket locked: no


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 14 years ago by danielk

(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.

comment:2 Changed 14 years ago by danielk

Component: dvbchannelscan

comment:3 Changed 13 years ago by danielk

Summary: Channel scanner problem when different channels have same ATSC major - ATSC minor valuesNon-unique ATSC channel numbers confuse channel scanner
Version: 0.20head

comment:4 Changed 12 years ago by Dibblah

Status: newassigned

comment:5 Changed 11 years ago by Janne Grunau

Milestone: unknown0.22
Resolution: fixed
Status: assignedclosed

should be fixed by channelscan merge

Note: See TracTickets for help on using tickets.