Opened 8 years ago

Last modified 11 months ago

#8732 assigned Bug Report - General

DVB-T scan: duplicate muxes created for MPEG channels

Reported by: Nick Morrott <knowledgejunkie (at) gmail (dot) com> Owned by: Stuart Auchterlonie
Priority: minor Milestone: 29.2
Component: MythTV - Channel Scanner Version: Master Head
Severity: medium Keywords: dvb-t mpeg duplicate multiplex
Cc: Ticket locked: no

Description

Using the same configuration as reported in #8726.

Scan details: full UK scan using Sutton Coldfield transmitter with 6 available muxes. Signal/tuning timeouts raised to 2000/6000ms. ALL services (DVB+MPEG) scanned, with decryption testing disabled.

During a successful DVB-T scan, all DVB channels are eventually discovered (although only 1 mux was successfully tuned during the initial scan phase and the remaining 5 muxes were found in the Network Information Table of the successfully scanned mux.)

However, although there are only 6 available muxes, 9 muxes are created in the database at the end of the scan.

Further checking reveals that the creation/configuration of the 4 MPEG channels found during the scan creates 3 new mux entries in the database, rather than configuring them with one of the existing mux entries used for the DVB channels on those muxes. Additionally, networkid is set to 0 on the additional muxes.

Full log output is attached to #8731

Change History (9)

comment:1 Changed 8 years ago by robertm

Owner: changed from danielk to Stuart Auchterlonie
Status: newassigned

comment:2 Changed 7 years ago by stuartm

Milestone: unknown0.26
Type: defectBug Report - General

I don't think this is going to get looked at for 0.25, not without a patch at least however it should be dealt with early in 0.26.

comment:3 Changed 6 years ago by Kenni Lund [kenni a kelu dot dk]

Milestone: 0.260.26.1

comment:4 Changed 5 years ago by paulh

Milestone: 0.26.10.28

comment:5 Changed 3 years ago by Stuart Auchterlonie

Milestone: 0.280.29

comment:6 Changed 3 years ago by Stuart Auchterlonie

Milestone: 0.2929.0

Milestone renamed

comment:7 Changed 13 months ago by Stuart Auchterlonie

Milestone: 29.029.1

comment:8 Changed 11 months ago by Stuart Auchterlonie

Milestone: 29.10.28.2

Moving remaining open tickets to 0.28.2 milestone

comment:9 Changed 11 months ago by Stuart Auchterlonie

Milestone: 0.28.229.2

Moving remaining open tickets to 29.2 milestone

Note: See TracTickets for help on using tickets.