Opened 11 years ago

Closed 11 years ago

#6500 closed defect (fixed)

New channel scanner can fill channel/dtv_multiplex with invalid values

Reported by: Anduin Withers Owned by: danielk
Priority: minor Milestone: 0.22
Component: MythTV - Channel Scanner Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

A normal cable qam-256 scan results in numerous dtv_multiplex entries with no 'frequency' and, in my case, only a single channel associated with the correct mplexid.

The information in channelscan_channel and channelscan_dtv_multiplex is correct.

Scan log with -v channel,siparser,channelscan,record attached.

Attachments (1)

broken_qam_scan.log.bz2 (196.5 KB) - added by Anduin Withers 11 years ago.
Channel scan log

Download all attachments as: .zip

Change History (6)

Changed 11 years ago by Anduin Withers

Attachment: broken_qam_scan.log.bz2 added

Channel scan log

comment:1 Changed 11 years ago by Anduin Withers

Milestone: unknown0.22
Version: unknownhead

comment:2 Changed 11 years ago by Matthias "mortalmatt" Dahl <devel@…>

This also happens to me with DVB-S. After importing a channels.conf into empty tables, the channel scan will fill up dtv_multiplex with a few dozen invalid transports (frequency = null) and the associations in channel (mplexid) is wrong too. Removing the invalid transports and starting a new scan results in a valid channels... AFAICT at the moment. The mappings seem to be right even though MythTV has a few problems w/ tuning now which it hasn't had before my crash yesterday.

comment:3 Changed 11 years ago by anonymous

Ok... I downgraded to SVN20426, imported a channels.conf to get the initial transponders and figured another difference: dtv_multiplex w/ current trunk lacks specific data for each transponder, most of them are left to auto (like modulation, fec, networkid, ...) which should explain my tuning problems after all.

comment:4 Changed 11 years ago by danielk

Status: newinfoneeded_new

Still happening? I fixed a Qt4 db bug yesterday that was causing invalid dtv_multiplex entries.

If it is still happening I need a dump of your three channelscan* tables for import here..

comment:5 Changed 11 years ago by danielk

Resolution: fixed
Status: infoneeded_newclosed

Pretty sure this was fixed the week before last. Please reopen if you can reproduce.

Note: See TracTickets for help on using tickets.