Bug #3846
Sometimes tvheadend does not want to tune to a channel
0%
Description
There are times when changing channels does work without any problems, but more often than not tvheadend seems to get into a state where it simply refuses to tune to a different channel. The strange thing is that if I subsequently use e.g. Kaffeine to tune to that same channel, Kaffeine is able to do so without problems. Afterwards, tvheadend also wants to tune to that channel again, and also other channels. I doubt signal strength is an issue, because both Kaffeine and tvheadend agree SRN is about 90%.
Log errors are of two kinds:
2016-06-07 21:39:50.232 mpegts: 12558V in Hotbird - tuning on Montage DS3103/TS2022 : DVB-S #0
2016-06-07 21:39:50.924 subscription: 0002: "192.168.2.102 [ pbienst | Kodi Media Center ]" subscribing on channel "JEEM Europe", weight: 150, adapter: "Montage DS3103/TS2022 : DVB-S #0", network: "Hotbird", mux: "12558V", provider: "Telespazio", service: "JEEM Europe", profile="htsp", hostname="192.168.2.102", username="pbienst", client="Kodi Media Center"
2016-06-07 21:39:58.745 TS: Hotbird/12558V/JEEM Europe: MPEG2VIDEO #2821 Continuity counter error (total 1)
#2822 Continuity counter error (total 1)
2016-06-07 21:39:58.745 TS: Hotbird/12558V/JEEM Europe: MPEG2AUDIO
2016-06-07 21:39:58.745 nit: invalid checksum (len 114, errors 1)
2016-06-07 21:39:58.834 TS: Hotbird/12558V/JEEM Europe Transport error indicator (total 1)
2016-06-07 21:39:58.915 pat: invalid checksum (len 80, errors 1)
2016-06-07 21:39:59.085 eit: invalid checksum (len 96, errors 1)
2016-06-07 21:39:59.418 pmt: invalid checksum (len 59, errors 1)
2016-06-07 21:39:59.908 cat: invalid checksum (len 3, errors 1)
2016-06-07 21:40:01.771 TS: Hotbird/12558V/JEEM Europe: MPEG2VIDEO #2821 Corrupted PES header (errors 1)
#2821 Continuity counter error (total 6523)
2016-06-07 21:40:03.771 bat: invalid checksum (len 527, errors 1)
2016-06-07 21:40:03.771 sdt: invalid checksum (len 527, errors 1)
2016-06-07 21:40:09.000 TS: Hotbird/12558V/JEEM Europe: MPEG2VIDEO
2016-06-07 21:40:09.000 TS: Hotbird/12558V/JEEM Europe: MPEG2AUDIO #2822 Continuity counter error (total 334)
#2821 Corrupted PES header (errors 7)
2016-06-07 21:40:09.096 pat: invalid checksum (len 80, errors 65)
2016-06-07 21:40:09.096 nit: invalid checksum (len 114, errors 58)
2016-06-07 21:40:09.354 TS: Hotbird/12558V/JEEM Europe Transport error indicator (total 42)
2016-06-07 21:40:10.095 pmt: invalid checksum (len 59, errors 68)
2016-06-07 21:40:10.544 eit: invalid checksum (len 96, errors 17)
2016-06-07 21:40:12.917 TS: Hotbird/12558V/JEEM Europe: MPEG2VIDEO
or sometimes simply
2016-06-05 13:17:15.451 subscription: 08FB: "192.168.2.102 [ pbienst | Kodi Media Center ]" unsubscribing from "zdf_neo HD", hostname="192.168.2.102", username="pbienst", client="Kodi Media Center"
2016-06-05 13:17:19.000 subscription: 0909: No input source available for subscription "192.168.2.102 [ pbienst | Kodi Media Center ]" to channel "CBBC HD"
Tuner is a DVB Sky 950C. Satellite is connected to a rotor system.
I've fiddled with many settings (tune repeats, skip initial bytes, ...) but to no avail...
History
Updated by P B over 8 years ago
I've done that, but it doesn't seem like this fundamentally changed things...
Updated by Jaroslav Kysela over 8 years ago
OK. Do you think that it's a rotor movement issue? Do you see this only when rotor is moved to a new position ?
Anyway, the driver returns a wrong MPEG-TS stream.. So you may also check the mux parameters, if they're correct.
Updated by P B over 8 years ago
I'm not sure it correlates with rotor movement. I've also reduced the rotor speed setting, so as to be sure the rotation has finished.
I've rescanned all the muxes yesterday. I guess that should have updated them to the correct values? Besides, it's not that a channel consistently fails, it only happens from time to time.
Are there extra debug options that would generate interesting logs?
Updated by P B over 8 years ago
The problem got successively worse and also occured in Kaffeine in the end. Replacing my tuner card seems to have fixed this problem, so this issue can be closed.