Project

General

Profile

Bug #1204

DVB multiplexes with same identifier

Added by jody gugelhop over 12 years ago. Updated about 12 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
3.2
Start date:
2012-09-04
Due date:
% Done:

0%

Estimated time:
Found in version:
3
Affected Versions:

Description

I'm using ubuntu 12.04 64 bit machine and a twin receiver card TBS 6991, tvheadend version is 3. I have two dishes one with one LNB and another dish with 2 LNB's. I use a disecq as well. When running tvheadend I get very often this error:

[ERROR]:dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_TurboSight_TBS_6991_DVBS_S2_frontend12640000_V_satconf_1" one is skipped

History

#1

Updated by Dave Chapman over 12 years ago

Just to be clear, you have one LNB connected to one tuner and two LNBs (via a diseqc switch) connected to the other tuner? What satellite positions are the three LNBs pointing to?

#2

Updated by Jelle De Loecker over 12 years ago

I'm running into the same problem.

I have 2 Technotrend 3200 cards, both connected to their own disecq switch with the same configuration:
1 - Astra 1
2 - Astra 2
3 - Astra 3
4 - Hotbird 13

This is the message I'm getting:

dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter1_STB0899_Multistandard12669500_V_satconf_2" one is skipped

I wonder: did lots of things change between the old version and the "reloaded" tvheadend that could cause problems with previous configurations?

#3

Updated by jody gugelhop over 12 years ago

Jelle De Loecker wrote:

I'm running into the same problem.

I have 2 Technotrend 3200 cards, both connected to their own disecq switch with the same configuration:
1 - Astra 1
2 - Astra 2
3 - Astra 3
4 - Hotbird 13

This is the message I'm getting:

dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter1_STB0899_Multistandard12669500_V_satconf_2" one is skipped

I wonder: did lots of things change between the old version and the "reloaded" tvheadend that could cause problems with previous configurations?

I removed and installed from scratch, until now this problem has not re-occurred, so yes it could be related to that, try the same as me and see if that works for you.

#4

Updated by Adam Sutton over 12 years ago

  • Status changed from New to Accepted
  • Assignee deleted (Hein Rigolo)

I think this is down to several possible causes, all of which will hopefully be addressed in 3.3.

1. We don't properly handle small variations in mux frequency and therefore keep updating them as the same thing.

2. We don't handle spot beams, meaning valid muxes are ignored as TVH currently assumes frequency alone is unique, when in fact you need to really include IDs (ONID/TSID).

My guess is this problem is caused by 2.

Adam

#5

Updated by Adam Sutton about 12 years ago

  • Status changed from Accepted to Fixed

I think this will probably be fixed by recent modifications to the mux registration.

Adam

#6

Updated by Adam Sutton about 12 years ago

  • Target version set to 3.2

Also available in: Atom PDF