Bug #5461
Feature #5460: deduplication of muxes and services
Tvheadend should not allow the creation of duplicate muxes
0%
Description
This bug report is related to feature request https://tvheadend.org/issues/5460
After going through the tedious job of manual deduplication of muxes and services,
I noticed the next scan brought back duplicate muxes immediately.
My manual deduplication was on one of my five DVBS networks, Astra 1 provided by
SAT>IP using a Telestar digibit R1 running satip-axe.
Before deduplication, almost every mux was duplicate, sometimes triple.
I deleted every service on Astra 1 not mapped to a channel, including hidden services.
I deleted every mux on Astra 1 with 0 services
For the remaining services, I carefully picked one mux and made notes of the channels that would be affected.
Then I forced a new scan, so I could re-map the now lost channel mappings.
Then I noticed the duplicate muxes coming back again.
These are muxes that are duplicate again:
10758.5V
11111.75H
11258.5H
11391.25H
History
Updated by Jaroslav Kysela almost 6 years ago
Updated by - Status changed from New to Rejected
- Parent task set to #5460
Updated by Jaroslav Kysela almost 6 years ago
Yes, there should be better way. You should mark the invalid muxes with the ignore flag at the moment - do not delete them.
Updated by Pim Zandbergen almost 6 years ago
Updated by But which one is invalid?
I closely compared a set and noticed the only difference was Stream ID.
The old one, with working mapped channels has Stream ID 0.
The newly created duplicate mux has Stream ID -1.
Updated by Jaroslav Kysela almost 6 years ago
The new default is -1 (no stream filter). You can just change this value for all muxes (assuming that you don't use multistream) and remove the new ones without services.