Bug #2670
Intolerance for short disturbances in DVB reception
0%
Description
A very short disturbance in DVB stream during HD channel reception causes long interruption on the screen. Sometimes it takes one or two minutes until Tvheadend recovers and the picture is shown on the screen.
In comparison with a Dreambox-like receiver it shows a block noise on the screen for not more than 0,1s then everything goes on.
In case of tvheadend the same disturbance causes block noise on the screen then there is a some second skip in picture and sound finally sometimes the reception stops for a while.
In these cases the recovery takes much longer time than switching back and forth to another channel.
In my case the source of disturbance is a dual output LNB. I have a second Tvheadend server which scans the satellites. When it switches to the LNB which is used by the primary Tvheadned server then it causes a short glitch.
I understand the the trigger is an external problem however I am convinced that Tvheadend should be much more robust against such disturbances.
Files
History
Updated by Jaroslav Kysela over 9 years ago
Updated by It may be related to descrambling in your case:
descrambler: NGC HD even stream key is not valid
Are you sure that your card reader is OK?
Updated by Akos Sz over 9 years ago
Updated by I think it is not reader related. See the oscam logs regarding the time period of last disturbance.
There are strange messages in the log, but the ECMs seem OK. I think even this oscam logs show that something went wrong in the client (tvheadend)
2015/02/08 18:43:48 14E3150 c anonymous (0653&000000/03F2/07E2/3C:A2C5AA8148B3C2440851B1A78F977873): found (106 ms) by TP-Link_server
2015/02/08 18:43:58 14E3150 c anonymous (0653&000000/03F2/07E2/3C:0687F5DF5C092461500E29B74CB5363D): found (121 ms) by TP-Link_server
2015/02/08 18:44:08 14E3150 c anonymous (0653&000000/03F2/07E2/3C:C9E096244B19FA371628E2403486EE37): found (111 ms) by TP-Link_server
2015/02/08 18:44:18 14E3150 c anonymous (0653&000000/03F2/07E2/3C:89E928B4CFCCD9BB2BD1029D2099B7C7): found (110 ms) by TP-Link_server
2015/02/08 18:44:28 14E3150 c anonymous (0653&000000/03F2/07E2/3C:CB17B76B5D05196E1073F6B8BAA2B593): found (115 ms) by TP-Link_server
2015/02/08 18:44:38 14E3150 c anonymous (0653&000000/03F2/07E2/3C:CEBA1F87FED110C6B98545530B303614): found (107 ms) by TP-Link_server
2015/02/08 18:44:48 14E3150 c anonymous (0653&000000/03F2/07E2/3C:A39BBFECD7DC89F2B3B96FDB0E045025): found (108 ms) by TP-Link_server
2015/02/08 18:44:58 14E3150 c anonymous (0653&000000/03F2/07E2/3C:7C5790C3F28A0848777331B939EE201A): found (126 ms) by TP-Link_server
2015/02/08 18:45:08 14E3150 c anonymous (0653&000000/03F2/07E2/3C:37BC4887EF0646FCA33D858F91296077): found (112 ms) by TP-Link_server
2015/02/08 18:45:10 14E3150 c [NEW ECMPID #0] CAID: 1880 ECM_PID: 18A9 PROVID: 000000
2015/02/08 18:45:10 14E3150 c [NEW ECMPID #1] CAID: 1802 ECM_PID: 18A8 PROVID: 000000
2015/02/08 18:45:10 14E3150 c Found 2 ECMpids and 0 STREAMpids in PMT
2015/02/08 18:45:10 14E3150 c [DVBAPI] Receiver wants to demux srvid 0FD2 on adapter 0000 camask 0001 index 0000 pmtpid 0000
2015/02/08 18:45:10 14E3150 c New program number: 0FD2 (1880:0FD2 unknown) [pmt_list_management 3]
2015/02/08 18:45:10 14E3150 c [DVBAPI] Found channel in cache -> start descrambling ecmpid #0
2015/02/08 18:45:10 14E3150 c [DVBAPI] Demuxer #0 trying to descramble PID #0 CAID 1880 PROVID 000000 ECMPID 18A9 ANY CHID PMTPID 0000 VPID 0003
2015/02/08 18:45:10 14E3150 c [DVBAPI] Demuxer #0 continue decoding of SRVID 0FD2
2015/02/08 18:45:10 14E3150 c [SKIP STREAM] CAID: 1880 ECM_PID: 18A9 PROVID: 000000 (Same as ECMPID #0)
2015/02/08 18:45:10 14E3150 c [SKIP STREAM] CAID: 1802 ECM_PID: 18A8 PROVID: 000000 (Same as ECMPID #1)
2015/02/08 18:45:10 14E3150 c Found 2 ECMpids and 0 STREAMpids in PMT
2015/02/08 18:45:10 14E3150 c [DVBAPI] Receiver wants to demux srvid 0FD2 on adapter 0000 camask 0001 index 0000 pmtpid 0000
2015/02/08 18:45:10 14E3150 c New program number: 0FD2 (1880:0FD2 unknown) [pmt_list_management 3]
2015/02/08 18:45:11 14E3150 c anonymous (1880&000000/0000/0FD2/89:48DE67BE8469788665F65207AAF9D105): found (98 ms) by TP-Link_server
2015/02/08 18:45:14 14E3150 c anonymous (1880&000000/0000/0FD2/89:257703AFA9B5CD15198068B9CB0CA107): found (900 ms) by TP-Link_server
2015/02/08 18:45:18 14E3150 c [NEW ECMPID #0] CAID: 0B02 ECM_PID: 072F PROVID: 000000
2015/02/08 18:45:18 14E3150 c [NEW ECMPID #1] CAID: 0653 ECM_PID: 072E PROVID: 000000
2015/02/08 18:45:18 14E3150 c [NEW ECMPID #2] CAID: 0D97 ECM_PID: 072D PROVID: 000000
2015/02/08 18:45:18 14E3150 c [NEW ECMPID #3] CAID: 0D02 ECM_PID: 072C PROVID: 000000
2015/02/08 18:45:18 14E3150 c [NEW ECMPID #4] CAID: 1815 ECM_PID: 072B PROVID: 000000
2015/02/08 18:45:18 14E3150 c [NEW ECMPID #5] CAID: 1880 ECM_PID: 072A PROVID: 000000
2015/02/08 18:45:18 14E3150 c [NEW ECMPID #6] CAID: 1802 ECM_PID: 0729 PROVID: 000000
2015/02/08 18:45:18 14E3150 c [NEW ECMPID #7] CAID: 0B1C ECM_PID: 0728 PROVID: 000000
2015/02/08 18:45:18 14E3150 c [NEW ECMPID #8] CAID: 1882 ECM_PID: 0727 PROVID: 000000
2015/02/08 18:45:18 14E3150 c Found 9 ECMpids and 0 STREAMpids in PMT
2015/02/08 18:45:18 14E3150 c [DVBAPI] Receiver wants to demux srvid 07E2 on adapter 0000 camask 0001 index 0000 pmtpid 0000
2015/02/08 18:45:18 14E3150 c New program number: 07E2 (0B02:07E2 unknown) [pmt_list_management 3]
2015/02/08 18:45:18 14E3150 c [DVBAPI] Found channel in cache -> start descrambling ecmpid #1
2015/02/08 18:45:18 14E3150 c [DVBAPI] Demuxer #0 trying to descramble PID #1 CAID 0653 PROVID 000000 ECMPID 072E ANY CHID PMTPID 0000 VPID 0004
2015/02/08 18:45:18 14E3150 c [DVBAPI] Demuxer #0 continue decoding of SRVID 07E2
2015/02/08 18:45:18 14E3150 c [SKIP STREAM] CAID: 0B02 ECM_PID: 072F PROVID: 000000 (Same as ECMPID #0)
2015/02/08 18:45:18 14E3150 c [SKIP STREAM] CAID: 0653 ECM_PID: 072E PROVID: 000000 (Same as ECMPID #1)
2015/02/08 18:45:18 14E3150 c [SKIP STREAM] CAID: 0D97 ECM_PID: 072D PROVID: 000000 (Same as ECMPID #2)
2015/02/08 18:45:18 14E3150 c [SKIP STREAM] CAID: 0D02 ECM_PID: 072C PROVID: 000000 (Same as ECMPID #3)
2015/02/08 18:45:18 14E3150 c [SKIP STREAM] CAID: 1815 ECM_PID: 072B PROVID: 000000 (Same as ECMPID #4)
2015/02/08 18:45:18 14E3150 c [SKIP STREAM] CAID: 1880 ECM_PID: 072A PROVID: 000000 (Same as ECMPID #5)
2015/02/08 18:45:18 14E3150 c [SKIP STREAM] CAID: 1802 ECM_PID: 0729 PROVID: 000000 (Same as ECMPID #6)
2015/02/08 18:45:18 14E3150 c [SKIP STREAM] CAID: 0B1C ECM_PID: 0728 PROVID: 000000 (Same as ECMPID #7)
2015/02/08 18:45:18 14E3150 c [SKIP STREAM] CAID: 1882 ECM_PID: 0727 PROVID: 000000 (Same as ECMPID #8)
2015/02/08 18:45:18 14E3150 c Found 9 ECMpids and 0 STREAMpids in PMT
2015/02/08 18:45:18 14E3150 c [DVBAPI] Receiver wants to demux srvid 07E2 on adapter 0000 camask 0001 index 0000 pmtpid 0000
2015/02/08 18:45:18 14E3150 c New program number: 07E2 (0B02:07E2 unknown) [pmt_list_management 3]
2015/02/08 18:45:18 14E3150 c anonymous (0653&000000/03F2/07E2/3C:EEA9D85A3CC61849D3D8A5F255D0E391): found (108 ms) by TP-Link_server
2015/02/08 18:45:28 14E3150 c anonymous (0653&000000/03F2/07E2/3C:B260B583BF8C0C4D87A252B61E151777): found (111 ms) by TP-Link_server
2015/02/08 18:45:38 14E3150 c anonymous (0653&000000/03F2/07E2/3C:1A8BA6C6F5D71D6DF7B004BCA1E0ABDB): found (116 ms) by TP-Link_server
2015/02/08 18:45:48 14E3150 c anonymous (0653&000000/03F2/07E2/3C:053143EA58BEAE6580482D6B2D9B2073): found (115 ms) by TP-Link_server
2015/02/08 18:45:58 14E3150 c anonymous (0653&000000/03F2/07E2/3C:15584F9761C9DE8347181BC39A6D7E87): found (115 ms) by TP-Link_server
2015/02/08 18:46:08 14E3150 c anonymous (0653&000000/03F2/07E2/3C:D4DD0A09117F96D05A7D67B8232CE47A): found (131 ms) by TP-Link_server
2015/02/08 18:46:18 14E3150 c anonymous (0653&000000/03F2/07E2/3C:9C088378BE9ACCB70CD934B0150D1132): found (111 ms) by TP-Link_server
2015/02/08 18:46:28 14E3150 c anonymous (0653&000000/03F2/07E2/3C:73575CDDE64B128BCF81FC8018C15AEA): found (111 ms) by TP-Link_server
2015/02/08 18:46:38 14E3150 c anonymous (0653&000000/03F2/07E2/3C:0B3E44B5669B15B5E4FD6B9D2F716BD9): found (111 ms) by TP-Link_server
2015/02/08 18:46:48 14E3150 c anonymous (0653&000000/03F2/07E2/3C:62AD25BE30EE9CBA73FB1B33EDCD05D3): found (117 ms) by TP-Link_server
2015/02/08 18:46:58 14E3150 c anonymous (0653&000000/03F2/07E2/3C:A3B866DD3DA12CEDC7D0A0DE80056192): found (108 ms) by TP-Link_server
2015/02/08 18:47:08 14E3150 c anonymous (0653&000000/03F2/07E2/3C:3C1273B6894CB10264183675BBC11D4A): found (112 ms) by TP-Link_server
2015/02/08 18:47:18 14E3150 c anonymous (0653&000000/03F2/07E2/3C:DEA966D40C8CA98EA8506C05D5CBB0BE): found (115 ms) by TP-Link_server
2015/02/08 18:47:28 14E3150 c anonymous (0653&000000/03F2/07E2/3C:28153657387509C0EF30DD49D3ADB54A): found (110 ms) by TP-Link_server
2015/02/08 18:47:38 14E3150 c anonymous (0653&000000/03F2/07E2/3C:95BF6BC926F4C730FE7F7C7F1DB6CEA7): found (106 ms) by TP-Link_server
2015/02/08 18:47:48 14E3150 c anonymous (0653&000000/03F2/07E2/3C:247048FB6A89300E670387AF05C0FCD1): found (109 ms) by TP-Link_server
2015/02/08 18:47:58 14E3150 c anonymous (0653&000000/03F2/07E2/3C:F891FB1C16DD3D64AFE6B20AC75C71BC): found (206 ms) by TP-Link_server
2015/02/08 18:48:08 14E3150 c anonymous (0653&000000/03F2/07E2/3C:84158D440513687BF95EDDD73C01B56C): found (111 ms) by TP-Link_server
2015/02/08 18:48:18 14E3150 c anonymous (0653&000000/03F2/07E2/3C:7DA71D2518A95419CF19ADFFC4D38267): found (113 ms) by TP-Link_server
2015/02/08 18:48:28 14E3150 c anonymous (0653&000000/03F2/07E2/3C:1029017545E6D27EF60EDEF243CA0887): found (120 ms) by TP-Link_server
2015/02/08 18:48:38 14E3150 c anonymous (0653&000000/03F2/07E2/3C:7F69287BDD4E461F2AD2E6165ABE44FE): found (110 ms) by TP-Link_server
2015/02/08 18:48:48 14E3150 c anonymous (0653&000000/03F2/07E2/3C:0B5DD4D13340D9C22666A3D57FB59E7F): found (124 ms) by TP-Link_server
2015/02/08 18:48:58 14E3150 c anonymous (0653&000000/03F2/07E2/3C:E39F3F9B1F8FF43461B8C5AAB32E28FA): found (112 ms) by TP-Link_server
2015/02/08 18:49:08 14E3150 c anonymous (0653&000000/03F2/07E2/3C:7DF417F03C28D0CB2F877043686D1943): found (108 ms) by TP-Link_server
Updated by Akos Sz over 9 years ago
On the other hand when I disable the tuner in the other server then there is no disturbance at all. When it is scanning I have problems in every minute.
Updated by Jaroslav Kysela over 9 years ago
Akos Sz wrote:
On the other hand when I disable the tuner in the other server then there is no disturbance at all. When it is scanning I have problems in every minute.
In this case, it seems that the input stream is broken and it may depend on tuner and drivers if they can minimize errors in reception. TVH cannot do much if you cannot get data from the hardware. You may dump the whole input stream using --tsdebug switch to analyze it, if you like.. If there are missing many MPEG-TS packets, then the fault is in the driver.
Updated by Akos Sz over 9 years ago
I wonder how the driver could cause this trouble since the channel switching is always fast and reliable.
Where can I find more info about using --tsdebug switch?
Which part does the buffering. Is it the driver, the tvheadend, the HTSP client or Kodi itself? I am asking because of the strange several second skip in the picture and sound.
Updated by Jaroslav Kysela over 9 years ago
Akos Sz wrote:
I wonder how the driver could cause this trouble since the channel switching is always fast and reliable.
It's something different. It seems - in your case - when there is a wrong reception, the hw/driver hangs for some seconds until the data recovers. The full initialization (channel switch) is different task.
Where can I find more info about using --tsdebug switch?
Compile tvheadend with --enable-tsdebug and use "--tsdebug <directory>" to store *input.ts file. This is exact contents which is read from the driver without any modifications from tvh. If you use FTA channels, you may play this contents back using vlc or any other media player. Also, you may use dvbsnoop to analyze TS files. Note that my experience is that small data lost (not so solid reception, but no totaly weak) does not do gaps in the streaming but only small picture artefacts are visible.
Which part does the buffering. Is it the driver, the tvheadend, the HTSP client or Kodi itself? I am asking because of the strange several second skip in the picture and sound.
You need to follow the whole chain - so start with the driver.
Updated by Akos Sz over 9 years ago
Hi,
I made some comparison tests with a TBS tuner card. I triggered the same disturbance by switching channel on the other receiver.
With TBS card I saw a very short disturbance on the screen in 1 out of 10 trials while Tevii card produced visible artifacts in all cases and the reception stopped for longer time at least three times.
This test clearly confirmed for me that Tevii s471 card and its linux driver are crappy.
The issue can be closed as not fault in tvheadend.
Updated by Mark Clarkstone over 9 years ago
Updated by Akos Sz wrote:
Hi,
I made some comparison tests with a TBS tuner card. I triggered the same disturbance by switching channel on the other receiver.
With TBS card I saw a very short disturbance on the screen in 1 out of 10 trials while Tevii card produced visible artifacts in all cases and the reception stopped for longer time at least three times.This test clearly confirmed for me that Tevii s471 card and its linux driver are crappy.
The issue can be closed as not fault in tvheadend.
Just to add, I have the Tevii S471 and have had no issues with the card or the drivers. There used to be a few bugs in kernels older than (I think) 3.8. However I did have interference at one point which was solved by keeping the LNB on and power saving disabled.
Also there is currently a regression in the latest media_tree with the cx23885 module which the Tevii S471 uses.