Bug #1586
Configuration mix-up by auto mux discovery
0%
Description
When the "Autodetect muxes" option is enabled on an adapter, it will also update already known muxes. However, there is something wrong in the mechanism, as this will sometimes mix things up and configures muxes with an wrong configuration (see below). This results in services beiing unavailable.
Also discussed (a bit) in this thread: https://www.lonelycoder.com/redmine/boards/5/topics/7037?r=7450
root@lbk-utr-rt01:/home/hts/.hts/tvheadend# grep '11,739,000' /var/log/syslog | grep 'updated by automatic mux discovery' | grep a21 | tail Jan 27 20:31:47 lbk-utr-rt01 tvheadend[6305]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a21 LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Jan 27 20:36:06 lbk-utr-rt01 tvheadend[6305]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a21 LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Jan 27 20:50:11 lbk-utr-rt01 tvheadend[17099]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a21 LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Jan 27 20:54:53 lbk-utr-rt01 tvheadend[17099]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a21 LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Jan 27 20:58:07 lbk-utr-rt01 tvheadend[17099]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a21 LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, ) Jan 27 20:59:39 lbk-utr-rt01 tvheadend[17099]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a21 LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, ) Jan 27 20:59:46 lbk-utr-rt01 tvheadend[17099]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a21 LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Jan 27 20:59:56 lbk-utr-rt01 tvheadend[17099]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a21 LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Jan 27 21:03:27 lbk-utr-rt01 tvheadend[17099]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a21 LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Jan 27 21:14:21 lbk-utr-rt01 tvheadend[17099]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a21 LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, )
root@lbk-utr-rt01:/home/hts/.hts/tvheadend# grep '11,739,000' /var/log/syslog | grep 'updated by automatic mux discovery' | grep a22 | tail Jan 27 14:56:29 lbk-utr-rt01 tvheadend[3262]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a22 LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Jan 27 14:56:49 lbk-utr-rt01 tvheadend[3262]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a22 LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Jan 27 15:01:50 lbk-utr-rt01 tvheadend[3262]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a22 LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Jan 27 15:02:48 lbk-utr-rt01 tvheadend[3262]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a22 LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Jan 27 15:06:35 lbk-utr-rt01 tvheadend[3262]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a22 LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Jan 27 15:08:15 lbk-utr-rt01 tvheadend[3262]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a22 LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, ) Jan 27 15:38:38 lbk-utr-rt01 tvheadend[3262]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a22 LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, ) Jan 27 15:50:38 lbk-utr-rt01 tvheadend[3262]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a22 LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Jan 27 15:51:38 lbk-utr-rt01 tvheadend[3262]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a22 LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Jan 27 21:32:07 lbk-utr-rt01 tvheadend[17099]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (a22 LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, )
In this case I could not get a lock on the channel on adapter22 because it changed the configuration with incorrect parameters.
When I adjusted the prio of the adapters, so that adapter21 would be chosen, the channel locks and streaming started.
To verify, I checked the configuration files of the adapters, and they match the output of the log file.
root@lbk-utr-rt01:/home/hts/.hts/tvheadend/dvbmuxes/_dev_dvb_adapter21_TurboSight_TBS_6984_DVBS_S2_frontend# cat _dev_dvb_adapter21_TurboSight_TBS_6984_DVBS_S2_frontend11739000_V_satconf_5
{
"quality": 100,
"enabled": 1,
"status": "Bad signal",
"transportstreamid": 3202,
"originalnetworkid": 3,
"network": "CANALDIGITAAL",
"frequency": 11739000,
"initialscan": 0,
"symbol_rate": 27500000,
"fec": "2/3",
"polarisation": "Vertical",
"modulation": "PSK_8",
"delivery_system": "SYS_DVBS2",
"rolloff": "ROLLOFF_25",
"satconf": "5"
}
root@lbk-utr-rt01:/home/hts/.hts/tvheadend/dvbmuxes# cat _dev_dvb_adapter22_TurboSight_TBS_6984_DVBS_S2_frontend/_dev_dvb_adapter22_TurboSight_TBS_6984_DVBS_S2_frontend11739000_V_satconf_8
{
"quality": 100,
"enabled": 1,
"status": "Faint signal",
"transportstreamid": 3202,
"originalnetworkid": 3,
"network": "CANALDIGITAAL",
"frequency": 11739000,
"initialscan": 0,
"symbol_rate": 27500000,
"fec": "3/4",
"polarisation": "Vertical",
"modulation": "QPSK",
"delivery_system": "SYS_DVBS",
"rolloff": "ROLLOFF_35",
"satconf": "8"
}
root@lbk-utr-rt01:/home/hts/.hts/tvheadend# cat dvbsatconf/_dev_dvb_adapter21_TurboSight_TBS_6984_DVBS_S2_frontend/5
{
"id": "5",
"port": 1,
"name": "a21 LNB2",
"comment": "a21 LNB2",
"lnb": "Universal"
}
root@lbk-utr-rt01:/home/hts/.hts/tvheadend# cat dvbsatconf/_dev_dvb_adapter22_TurboSight_TBS_6984_DVBS_S2_frontend/8
{
"id": "8",
"port": 1,
"name": "a22 LNB2",
"comment": "a22 LNB2",
"lnb": "Universal"
}
Files
History
Updated by Adam Sutton almost 12 years ago
Updated by - Status changed from New to Accepted
I can see what is happening and its a long standing issue. Both sets of params are correct, the sats involved have both of those mux configs on the same freq. But as 2 diff spot beams. one aimed at the uk the other Netherlands.
I'm not sure this will be fixed soon, but I'll take a look.
Adam
Updated by Hugo Rodenburg almost 12 years ago
Updated by I understand what you're saying about the spotbeam. However, I am unable to find that beam/info on sites such as lyngsat or kingofsat. They should list that transponder on the 23.5 position right? (this issue is about a transponder on 23.5)
What I did notice however is the following.
My configuration consists of 3 lnb's aimed at 19.2,23.5 and 28.5, connected to a diseqc switch. The issue above is about LNB2, which is 23.5.
The updated configuration is incorrect for the transponder on 23.5 (as of my opinion). However, it exactly does match the transponder on 19.2! (http://www.lyngsat.com/Astra-1KR-1L-1M-2C.html)
Is it possible that there is something wrong with the selection of the port on the diseqc switch, and tvheadend "thinks" 23.5 is selected (port 2) when in fact 19.2 (port 1) is selected.
I have triple-checked my diseqc configuration, and seems ok to me.
Updated by Adam Sutton almost 12 years ago
You're right that this is two diff satellites (and also diff IDs), but my point was that TVH simply doesn't deal with these properly at the moment. There possibly is a quicker fix for this particular issue than I'd first thought. I think the issue is possibly that its not searching properly and only using ONID/TSID.
However given the DVB code is in the process of being re-written its unlikely it will be fixed before that. But I'll have another check to see if there is actually a genuine mistake (as opposed to a limitation in the fundamental structures used within TVH).
Adam
Updated by Adam Sutton almost 12 years ago
One other thing you could try that would be useful to see, is enable the extra debug I've put in the table processing.
CFLAGS=-DTDT_TRACE ./configure; make
And run with -d and capture the logging etc.. What I want to see is whether the bug is that the satconf is not being properly copied across OR that the NIT information actually contains both. I suspect the former, or some variation on that.
Adam
Updated by Adam Sutton almost 12 years ago
Oh and where it is changing the satconf incorrectly, can you provide a full debug log, not a grepped one.
Ta
Adam
Updated by Adam Sutton almost 12 years ago
Hugo,
I've been reading #1416, and I think the two issues might be related. I'm still not 100% sure this will fix things, but can you take a look at this patch: http://pastebin.com/Sf7YFSvQ.
Ta
Adam
Updated by Adam Sutton over 11 years ago
I really need to get some feedback on this if possible. I think its probable that the fixes now in master should solve this, but I cannot test it myself.
Ta
Adam
Updated by Hugo Rodenburg over 11 years ago
- File tvheadend.log.gz tvheadend.log.gz added
Hi Adam,
I've applied the patch on my testing system a few days ago to let it run for a few days to see what happens. This system has an TBS6981 card, attached to the same dish configuration
LNB1: 19.2
LNB2: 23.5
LNB3: 28.5 (not configured in tvheadend)
I did not yet had the time to examine the changes, but i'm looking briefly at the moment and it seems definitly something has changed.
When searching for the frequency mentioned above, I now see the following output:
# grep '11,739,000' syslog | grep LNB2 Feb 15 08:20:37 scanserver tvheadend[3144]: dvb: "/dev/dvb/adapter1" tuning via s2api to "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" (1139000, 27500000 Baud, 3/4, SYS_DVBS, QPSK) for Autoscan Feb 15 08:20:52 scanserver tvheadend[3144]: dvb: "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" on adapter "TurboSight adapter1", status changed to Faint signal Feb 15 08:20:53 scanserver tvheadend[3144]: dvb: "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" on adapter "TurboSight adapter1", status changed to Bad signal Feb 15 08:20:54 scanserver tvheadend[3144]: dvb: "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" on adapter "TurboSight adapter1", status changed to Faint signal Feb 15 08:22:28 scanserver tvheadend[3144]: dvb: Configuration for mux "Skylink: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Feb 15 08:22:53 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 08:23:27 scanserver tvheadend[3144]: dvb: Configuration for mux ": 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 08:26:42 scanserver tvheadend[3144]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Feb 15 08:43:30 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Feb 15 08:52:16 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Feb 15 08:58:23 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, ) Feb 15 08:59:47 scanserver tvheadend[3144]: dvb: Configuration for mux ": 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, ) Feb 15 09:00:34 scanserver tvheadend[3144]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 09:01:58 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Feb 15 09:25:14 scanserver tvheadend[3144]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Feb 15 09:37:36 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Feb 15 09:43:22 scanserver tvheadend[3144]: dvb: Configuration for mux "Skylink: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Feb 15 09:46:33 scanserver tvheadend[3144]: dvb: Configuration for mux "Towercom, a.s.: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 09:50:45 scanserver tvheadend[3144]: dvb: "/dev/dvb/adapter1" tuning via s2api to "Towercom, a.s.: 11,739,000 kHz Vertical (LNB2)" (1139000, 27500000 Baud, 2/3, SYS_DVBS2, PSK_8) for Autoscan Feb 15 09:50:47 scanserver tvheadend[3144]: dvb: "Towercom, a.s.: 11,739,000 kHz Vertical (LNB2)" on adapter "TurboSight adapter1", status changed to OK Feb 15 09:50:47 scanserver tvheadend[3144]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 09:52:53 scanserver tvheadend[3144]: dvb: Configuration for mux "Skylink: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 09:53:01 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 09:53:37 scanserver tvheadend[3144]: dvb: Configuration for mux ": 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 09:56:34 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Feb 15 10:32:32 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Feb 15 10:38:24 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, ) Feb 15 10:39:57 scanserver tvheadend[3144]: dvb: Configuration for mux ": 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, ) Feb 15 10:40:47 scanserver tvheadend[3144]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 10:42:09 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Feb 15 11:04:44 scanserver tvheadend[3144]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Feb 15 11:17:26 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Feb 15 11:23:07 scanserver tvheadend[3144]: dvb: Configuration for mux "Skylink: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Feb 15 11:31:06 scanserver tvheadend[3144]: dvb: "/dev/dvb/adapter1" tuning via s2api to "Towercom, a.s.: 11,739,000 kHz Vertical (LNB2)" (1139000, 27500000 Baud, 2/3, SYS_DVBS2, PSK_8) for Autoscan Feb 15 11:31:08 scanserver tvheadend[3144]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 11:33:00 scanserver tvheadend[3144]: dvb: Configuration for mux "Skylink: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 11:33:17 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 11:33:57 scanserver tvheadend[3144]: dvb: Configuration for mux ": 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 11:36:52 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Feb 15 11:53:45 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, ) Feb 15 12:03:12 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, SYS_DVBS->SYS_DVBS2, ROLLOFF_35->ROLLOFF_25, ) Feb 15 12:09:01 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, ) Feb 15 12:10:17 scanserver tvheadend[3144]: dvb: Configuration for mux ": 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( QPSK->PSK_8, ) Feb 15 12:10:58 scanserver tvheadend[3144]: dvb: Configuration for mux "CANALDIGITAAL: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery Feb 15 12:12:17 scanserver tvheadend[3144]: dvb: Configuration for mux "ASTRA 3: 11,739,000 kHz Vertical (LNB2)" updated by automatic mux discovery ( PSK_8->QPSK, SYS_DVBS2->SYS_DVBS, ROLLOFF_25->ROLLOFF_35, )
I've attached the full tvheadend log (gzipped) with the trace/debug info (compiled with trace options as requested).
If you need more information I will happy to supply.
Hugo
Updated by Adam Sutton over 11 years ago
Hugo,
Did you flush you're old configuration? I'm just going through the log and it appears to me that everything is being listed as using (LNB2). What I'm unsure about is whether than indicates a problem still exists (and its overwriting that, which I'm looking at now) OR whether this is left over from the previous bug and you've just not flushed the config and started again.
Adam
Updated by Adam Sutton over 11 years ago
Ideally what I need to see is a run, from fresh, for the entire setup process (with TRACE enabled) so I can see what happens and when for all muxes. yes I know it'll be a big file 
Adam
Updated by Hugo Rodenburg over 11 years ago
Hi Adam,
Yes offcourse I should have flushed my old config. You're right, I didn't do that, sorry.
Now I've recreated the config (stop tvheadend, deleted the dvb* directories, start tvheadend, add LNB config, add standard muxes, make sure "autodetect muxes" is turned on.) and let it discover.
See the attached file for the complete log.
Please let me know if you need anything else.
Hugo
Updated by Adam Sutton over 11 years ago
- Status changed from Need feedback to Fixed
- Target version set to 3.4
I think this should have been fixed by all the recent updates to remove stale data from SI table pipelines. If this is not the case please shout.
Adam