Project

General

Profile

Bug #2682

Same MUX was added twice

Added by Dave Nowak almost 10 years ago. Updated almost 10 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
Service Mapping
Target version:
-
Start date:
2015-02-16
Due date:
% Done:

100%

Estimated time:
Found in version:
v3.9-2499-g51e9aec
Affected Versions:

Description

Some MUXes are added twice and the difference is in frequency, like: 11875H and 11875.5H - the effect is that some services exist twice and are added to channels twice as well. See screenshot

Files

muxes.png (84.9 KB) muxes.png two same muxes with slightly different frequency - 11875H and 11875.5H Dave Nowak, 2015-02-16 20:54

History

#1

Updated by Jaroslav Kysela almost 10 years ago

Some of these muxes (probably old 11875H - QPSK in this case) should be marked as FAIL for the scan status after new scan (you may even force scan). Remove these muxes in the mux grid (table). They should not appear again, or if they appear (the provider forgot to clean/update the info tables), the muxes should have no assigned services.

I improved the check for dead muxes, so they won't be updated from NIT and SDT tables now.

#2

Updated by Jaroslav Kysela almost 10 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset commit:tvheadend|496e4b1f0081f5ca848874b45e2719a408776544.

#3

Updated by Dave Nowak almost 10 years ago

I am sorry, it does not work for me. I deleted all muxes, under Networks I chose Predefined Muxes: 23E5 and Force scan. It started with (44 MUXes or so) and I ended with 74 MUXes and 11875H and 11875.5H are there again. It may be that I did something wrong... I am not sending the screenshot because it would be the same I posted yesterday.

#4

Updated by Dave Nowak almost 10 years ago

I forgot to mention that I updated to trunk.

#5

Updated by Jaroslav Kysela almost 10 years ago

OK, the scanfile (Astra-23.5E file) has this old entry:

[CHANNEL]
        DELIVERY_SYSTEM = DVBS
        FREQUENCY = 11875000
        POLARIZATION = HORIZONTAL
        SYMBOL_RATE = 27500000
        INNER_FEC = 3/4
        INVERSION = AUTO

But on this frequency is new mux:

[  DEBUG]:nit:     DVBS2 23.5E freq 11875500 H sym 29900000 fec 3/4 mod PSK/8 roff 20 is_id -1 pls_mode ROOT pls_code 0

So the mux from the scan tables should be marked with the scan status 'FAIL' with zero services, because it is no longer valid.

You have basically two ways to handle this:

1) send an update to the dtv scan tables maintainer - we take scanfiles from http://linuxtv.org/git/dtv-scan-tables.git
2) remove the muxes marked as 'FAIL', they won't be scanned again... (update: unless the broadcaster advertises them)

Also available in: Atom PDF