Bug #3253
Duplicate muxes (?) and problems in mapping from bouquets
0%
Description
I'm using enigma2 bouquets and they work well for me until now. Today I've just seen that some channels disappeared from my list so I compared the data from the enigma2 list with the information on the services: they matched but there were other strange facts.
The disappeared channels belong to the 10930H mux of Hotbird 13°: I had two muxes with such frequency with a lot of services (too many) for each: see screenshot n.1. With this state, the auto-mapping of enigma2 bouquets didn't work.
I then deleted both the muxes and forced a scan on all the muxes: after few minutes both the muxes appeared again and after their scan I can see few services for each and automapping started to work again.
Is it regular to have duplicates mux for the same frequency with duplicate services (not all)? The parameters are different: see screenshot n.2.
For the big number of spurious services: is it just regular or there are some non-detected duplicate information?
Files
History
Updated by Jaroslav Kysela about 9 years ago
Updated by One mux should fail. The parameters are totally different. It's something with the tuner ?
Updated by Mario D about 9 years ago
Updated by 
It is an Octopus Net SAT>IP tuner.
You mean that there should not exist two muxes with (almost) same frequency and same TSID? I have many of them.
Updated by Jaroslav Kysela about 9 years ago
Uff.. It looks like a serious error. The muxes on pictures have so different parameters so the tuner must not tune to them. Appearently, Octopus is trying to guess something which is bad. But thinking more - the SAT>IP servers should return the tuned parameters (TVH ignores them at the moment). Perhaps, we should do checking.
Could you provide trace from 'satip' subsystem when you mark these two muxes as scan pending ? I'm looking for 'Status string:' lines.
Updated by Mario D about 9 years ago
Just for the records: on Hotbird 13° I got 123 muxes and 25472 services... 
Updated by Jaroslav Kysela about 9 years ago
- Status changed from New to Rejected
satip: setup params - src=1&fe=1&freq=10930.16&sr=30000&msys=dvbs2&mtype=8psk&pol=h&fec=23&ro=0.20&pids=0 satip: Status string: 'ver=1.0;src=1;tuner=1,204,1,12,10930,h,dvbs2,8psk,,0.20,30000,23;pids=0,16,17,18'
satip: setup params - src=1&fe=1&freq=10930.16&sr=29900&msys=dvbs&mtype=qpsk&pol=h&fec=34&ro=0.35&pids=0 satip: Status string: 'ver=1.0;src=1;tuner=1,204,1,12,10930,h,dvbs,qpsk,,0.35,29900,34;pids=0,16,17,18'
Do you see the issue ? The server lies... It's impossible to have two muxes on same frequency and polarization. You should report this to vendor. Anyway, I suggest to disable the "phantom" muxes. A lot of manual work, I know.
Updated by Jaroslav Kysela about 9 years ago
Note: Disable - not delete. If you have autodiscovery on - they'll be created again...
Updated by Mario D about 9 years ago
Just reported: I hope in a technical reply.
How can I recognize the "phantom" mux to disable?
Updated by Jaroslav Kysela about 9 years ago
Check double TSIDs and then http://lyngsat.com which tuning parameters are valid.
The problem is that broadcasters "forgot" to update some muxes and they're broadcasting older parameters on them.
Updated by Mario D about 9 years ago
- File schermata n.5.png schermata n.5.png added
- File schermata n.4.png schermata n.4.png added
- File schermata n.3.png schermata n.3.png added
This story is totally crazy: about 50% of my mux have duplicates and many success both...
The duplicate are sometimes on different frequencies or on different polarization (see screenshots n.3-5).
The reported set of services coincides or one is a subset of the other.