Feature #3629
Descambling errors not detected for recordings
100%
Description
Hi folks,
I noticed that recordings show up as finshed w/o any error, even if descrambling failed completely.
Example:
oscam.log when the recording starts:
2016/03/11 20:58:30 2F08621D c (dvbapi) Demuxer 0 ecmpid 0 CAID: 098C ECM_PID: 1A0E PROVID: 000000
2016/03/11 20:58:30 2F08621D c (dvbapi) Demuxer 0 ecmpid 1 CAID: 09AF ECM_PID: 1F0E PROVID: 000000
2016/03/11 20:58:30 2F08621D c (dvbapi) Demuxer 0 ecmpid 2 CAID: 09C4 ECM_PID: 1B0E PROVID: 000000
2016/03/11 20:58:30 2F08621D c (dvbapi) Demuxer 0 found 3 ECMpids and 1 STREAMpids in PMT
2016/03/11 20:58:30 2F08621D c (dvbapi) Demuxer 0 serving srvid 006E (Sky Atlantic HD) on adapter 0001 camask 0002 index 0000 pmtpid 0000
2016/03/11 20:58:30 2F08621D c (dvbapi) Demuxer 0 no suitable readers found that can be used for decoding!
2016/03/11 20:58:34 2F08621D c (dvbapi) Demuxer 0 no enabled matching ecmpids > decoding is waiting for matching readers!) -- Skipped 13 duplicated log lines --
2016/03/11 20:59:44 2F08621D c (
tvheadend log for the recording in question:
2016-03-11 20:58:30.002 [ DEBUG]:capmt: Dude CAPMT: Trying to obtain key for service "Sky Atlantic HD"
2016-03-11 20:58:30.003 [ INFO]:subscription: 2072: "DVR: House of Cards" subscribing on channel "Sky Atlantic", weight: 300, adapter: "SAT>IP DVB-S Tuner #4 (192.168.178.34)", network: "Astra 19.2", mux: "11992.5H", provider: "SKY", service: "Sky Atlantic HD", profile="pass"
2016-03-11 20:58:30.024 [ DEBUG]:satip: 192.168.178.34 #4 - new session 842C3FC8 stream id 813
2016-03-11 20:58:30.052 [ DEBUG]:mpegts: 11992.5H in Astra 19.2 - open PID 0000 (0) [20/0x2c0e680]
2016-03-11 20:58:30.052 [ DEBUG]:mpegts: 11992.5H in Astra 19.2 - open PID 0001 (1) [16/0x2c36210]
2016-03-11 20:58:30.052 [ DEBUG]:mpegts: 11992.5H in Astra 19.2 - open PID 0010 (16) [16/0x2d424c0]
2016-03-11 20:58:30.052 [ DEBUG]:mpegts: 11992.5H in Astra 19.2 - open PID 0011 (17) [20/0x3b8bed0]
2016-03-11 20:58:30.052 [ DEBUG]:mpegts: 11992.5H in Astra 19.2 - open PID 0011 (17) [16/0x4d62480]
2016-03-11 20:58:30.276 [ DEBUG]:service: Astra 19.2/11992.5H/Sky Atlantic HD: Status changed to [Hardware input]
2016-03-11 20:58:30.276 [ DEBUG]:service: Astra 19.2/11992.5H/Sky Atlantic HD: Status changed to [Hardware input] [Input on service]
2016-03-11 20:58:30.276 [ DEBUG]:service: Astra 19.2/11992.5H/Sky Atlantic HD: Status changed to [Hardware input] [Input on service] [No access]
2016-03-11 20:58:30.276 [ DEBUG]:service: Astra 19.2/11992.5H/Sky Atlantic HD: Status changed to [Hardware input] [Input on service] [Demuxed packets] [No access]
2016-03-11 20:58:30.276 [ DEBUG]:service: Astra 19.2/11992.5H/Sky Atlantic HD: Status changed to [Hardware input] [Input on service] [Demuxed packets] [Reassembled packets] [No access]
complete log here: http://paste.ubuntu.com/15383610
Afterwards the recording is marked 100% ok. I would like to see an increased error count to be used for triggering automatic re-recordings.
Thanks in advance
Rich
History
Updated by Jaroslav Kysela over 8 years ago
Updated by There are several things - it's not so straight that you think:
1) there are TELETEXT data for example which are fine (non-descrambled)
2) TVH tries to hide the descrambling errors on start (sometimes, keys are not available quickly)
But I found some logic errors in the code and added forced TS data error processing after 30 seconds when the first TS packet is received.
Fixed in v4.1-1678-gae6c645 . Also, when data errors reaches threshold 10000, the recordings is marked as 'Too many data errors' and it's in the failed grid.
Updated by Jaroslav Kysela over 8 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset commit:tvheadend|4b6c25a5b86d72a9747451d419c1fb67df4ac887.