Bug #4303: Tvheadend don't switch to the next service when descrambling fail - Tvheadend

Bug #4303

Tvheadend don't switch to the next service when descrambling fail

Added by ian stuart over 7 years ago. Updated over 7 years ago.

Status:

Fixed

Priority:

Normal

Assignee:

Category:

Infrastructure

Target version:

Start date:

2017-03-30

Due date:

% Done:

100%

Estimated time:

Found in version:

4.1.x

Affected Versions:

Description

Hi,

I have:
- DVB-S card with 8 tunners ~~> Satellite (with priority 300)~~
DVB-C card with 4 tunners ~~> Cable (with priority 200)~~
DVB-T card with 4 tunners -> TNT (with priority 100)

Satellite have the highest priority, so it's used first.
It uses a (official !) smartcard with OSCam.

Sometime the provider smartcard fail to handle (unscramble) 2 or more channels in the same time.
So imagine i want to watch "Discovery channel"
I expect Tvheadend to switch to the next service (in my case, "Discovery channel" on DVB-C with priority 200) but it's not the case.
It fail with something like " Unable to unscramble this channel " and just stop. (Note i'd unchecked "Continue even if descrambling fails", as i don't want to wait minutes or hours until smartcard can handle again my stream).

I know it's should works because i had tested this behavior with IPTV, DVB-C and DVB-T.
If the IPTV link don't works, Tvheadend just uses the next service (DVB-C in my case)
If DVB-C can't handle, it switch to the next service (DVB-T), which is just (one of) the best functionality in Tvheadend !

I hope it will be fixed soon !

Thanks for all your work, we love you devs !

Files

trace_with_continious_descrambling.txt (4.69 KB) trace_with_continious_descrambling.txt		Thorsten Krohn, 2017-04-05 09:03
trace_without_continious_descrambling.txt (16.4 KB) trace_without_continious_descrambling.txt		Thorsten Krohn, 2017-04-05 09:03
trace_with_change_service_set.txt (10.5 KB) trace_with_change_service_set.txt		Thorsten Krohn, 2017-04-05 09:39
trace_service_change_on descramble_fail_.txt (48.3 KB) trace_service_change_on descramble_fail_.txt		Thorsten Krohn, 2017-04-05 17:37
trace_service_change_on descramble_fail_1.txt (118 KB) trace_service_change_on descramble_fail_1.txt		Thorsten Krohn, 2017-04-05 19:14
trace_service_change_on descramble_fail_2.txt (75.2 KB) trace_service_change_on descramble_fail_2.txt		Thorsten Krohn, 2017-04-05 19:46
trace_service_change_on descramble_fail_3.txt (25.2 KB) trace_service_change_on descramble_fail_3.txt		Thorsten Krohn, 2017-04-05 20:14
trace01.txt (18.7 KB) trace01.txt		ian stuart, 2017-04-06 00:38
trace_service_change_on_descramble_fail_4.txt (69.8 KB) trace_service_change_on_descramble_fail_4.txt		Thorsten Krohn, 2017-04-06 08:50

History

Updated by Jaroslav Kysela over 7 years ago

Provide '--trace service,subscription' - https://tvheadend.org/projects/tvheadend/wiki/Traces for this situation.

Updated by ian stuart over 7 years ago

Sure... Tell me if you need anything else.

2017-03-30 16:16:06.384 [ TRACE]:subscription: 0406: creating subscription for TV BREIZH weight 0 using profile pass 2017-03-30 16:16:06.384 [ TRACE]:subscription: 0406: find service for TV BREIZH weight 100 2017-03-30 16:16:06.384 [ DEBUG]:service: 1: TV BREIZH si 0x7f61d80f7a90 <unknown> weight 0 prio 40 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 1: TV BREIZH si 0x7f61d800afa0 <unknown> weight 0 prio 50 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 22: TV BREIZH si 0x7f61d8001580 Silicon Labs Si2168 : DVB-C #0 weight 0 prio 210 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 19: TV BREIZH si 0x7f61d8032a60 Silicon Labs Si2168 : DVB-C #0 weight 0 prio 210 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 16: TV BREIZH si 0x7f61d80ea750 Silicon Labs Si2168 : DVB-C #0 weight 0 prio 210 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 13: TV BREIZH si 0x7f61d808d0b0 Silicon Labs Si2168 : DVB-C #0 weight 0 prio 210 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 8: TV BREIZH si 0x7f61d8019a00 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 4: TV BREIZH si 0x7f61d8164d90 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 33: TV BREIZH si 0x7f61d8020dd0 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 7: TV BREIZH si 0x7f61d811d490 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 6: TV BREIZH si 0x7f61d8005ec0 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 5: TV BREIZH si 0x7f61d81005d0 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 3: TV BREIZH si 0x7f61d8066840 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:06.384 [ DEBUG]:service: 2: TV BREIZH si 0x7f61d80080e0 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:06.384 [ TRACE]:service: will start new instance 4 2017-03-30 16:16:06.384 [ TRACE]:service: starting astra 19.2/12402V/TV BREIZH 2017-03-30 16:16:06.384 [ INFO]:mpegts: 12402V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 2017-03-30 16:16:06.425 [ INFO]:capmt: xxx: Starting CAPMT server for service "TV BREIZH" on adapter 13 2017-03-30 16:16:06.425 [ TRACE]:subscription: 0406: linking sub 0x7f60c0001210 to svc 0x555c5c8b6dc0 type 0 2017-03-30 16:16:06.426 [ INFO]:subscription: 0406: "HTTP" subscribing on channel "TV BREIZH", weight: 100, adapter: "TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0", network: "astra 19.2", mux: "12402V", provider: "CSAT", service: "TV BREIZH", profile="pass", hostname="xxx", username="xxx", client="VLC/2.2.2 LibVLC/2.2.2" 2017-03-30 16:16:06.426 [ TRACE]:subscription: 0406: chain 01: input 2017-03-30 16:16:06.426 [ TRACE]:subscription: 0406: chain 02: streaming queue 0x7f61de7fb268 size 0 2017-03-30 16:16:06.426 [ INFO]:capmt: xxx: mode 6 sockfile /tmp/camd.socket got connection from client (single) 2017-03-30 16:16:06.426 [ INFO]:capmt: xxx: Connected to server 'OSCam v1.20-unstable_svn, build r11380 (x86_64-linux-gnu-pcsc)' (protocol version 2) 2017-03-30 16:16:06.812 [ DEBUG]:service: astra 19.2/12402V/TV BREIZH: Status changed to [Hardware input] 2017-03-30 16:16:06.812 [ DEBUG]:service: astra 19.2/12402V/TV BREIZH: Status changed to [Hardware input] [Input on service] 2017-03-30 16:16:06.812 [ DEBUG]:service: astra 19.2/12402V/TV BREIZH: Status changed to [Hardware input] [Input on service] [No access] 2017-03-30 16:16:07.012 [ DEBUG]:service: astra 19.2/12402V/TV BREIZH: Status changed to [Hardware input] [Input on service] [Demuxed packets] [No access] 2017-03-30 16:16:07.012 [ DEBUG]:service: astra 19.2/12402V/TV BREIZH: Status changed to [Hardware input] [Input on service] [Demuxed packets] [Reassembled packets] [No access] 2017-03-30 16:16:09.991 [ DEBUG]:service: 10758.5V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:09.991 [ INFO]:mpegts: 10758.5V in astra 19.2 - scan no data, failed 2017-03-30 16:16:09.991 [ INFO]:subscription: 03FD: "scan" unsubscribing 2017-03-30 16:16:09.991 [ INFO]:mpegts: 11739V in astra 19.2 scan complete 2017-03-30 16:16:09.991 [ INFO]:subscription: 03FE: "scan" unsubscribing 2017-03-30 16:16:10.115 [ DEBUG]:service: 10906V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:10.115 [ INFO]:mpegts: 10906V in astra 19.2 - scan no data, failed 2017-03-30 16:16:10.115 [ INFO]:subscription: 0404: "scan" unsubscribing 2017-03-30 16:16:10.115 [ DEBUG]:service: 11538V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:10.115 [ INFO]:mpegts: 11538V in astra 19.2 - scan no data, failed 2017-03-30 16:16:10.115 [ INFO]:subscription: 0403: "scan" unsubscribing 2017-03-30 16:16:10.115 [ DEBUG]:service: 11567.5V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:10.115 [ INFO]:mpegts: 11567.5V in astra 19.2 - scan no data, failed 2017-03-30 16:16:10.115 [ INFO]:subscription: 0402: "scan" unsubscribing 2017-03-30 16:16:10.115 [ DEBUG]:service: 11317.5V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:10.115 [ INFO]:mpegts: 11317.5V in astra 19.2 - scan no data, failed 2017-03-30 16:16:10.115 [ INFO]:subscription: 0401: "scan" unsubscribing 2017-03-30 16:16:10.738 [ INFO]:mpegts: 12402V in astra 19.2 scan complete 2017-03-30 16:16:20.683 [ TRACE]:subscription: 0407: creating subscription for service 12480V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:20.683 [ TRACE]:subscription: 0407: find instance for 12480V in astra 19.2 weight 2 2017-03-30 16:16:20.683 [ DEBUG]:service: 33: 12480V in astra 19.2 si 0x7f61d80069b0 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.683 [ DEBUG]:service: 8: 12480V in astra 19.2 si 0x7f61d81648e0 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.683 [ DEBUG]:service: 7: 12480V in astra 19.2 si 0x7f61d8035e90 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.683 [ DEBUG]:service: 6: 12480V in astra 19.2 si 0x7f61d800b5e0 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.683 [ DEBUG]:service: 5: 12480V in astra 19.2 si 0x7f61d806a8c0 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.683 [ DEBUG]:service: 3: 12480V in astra 19.2 si 0x7f61d806dec0 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.683 [ DEBUG]:service: 2: 12480V in astra 19.2 si 0x7f61d8002980 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.683 [ DEBUG]:service: 4: 12480V in astra 19.2 si 0x7f61d8032280 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:20.683 [ TRACE]:service: will start new instance 2 2017-03-30 16:16:20.683 [ TRACE]:service: starting 12480V in astra 19.2 2017-03-30 16:16:20.683 [ INFO]:mpegts: 12480V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 2017-03-30 16:16:20.703 [ TRACE]:subscription: 0407: linking sub 0x7f61d8005780 to svc 0x7f61d8004490 type 1 2017-03-30 16:16:20.703 [ INFO]:subscription: 0407: "scan" subscribing to mux "12480V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:20.703 [ TRACE]:subscription: 0407: chain 01: input 2017-03-30 16:16:20.703 [ TRACE]:subscription: 0407: chain 02: null input 2017-03-30 16:16:20.703 [ TRACE]:subscription: 0408: creating subscription for service 12324V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:20.703 [ TRACE]:subscription: 0408: find instance for 12324V in astra 19.2 weight 2 2017-03-30 16:16:20.703 [ DEBUG]:service: 33: 12324V in astra 19.2 si 0x7f61d8165430 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.703 [ DEBUG]:service: 8: 12324V in astra 19.2 si 0x7f61d8009dc0 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.703 [ DEBUG]:service: 7: 12324V in astra 19.2 si 0x7f61d811d210 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.703 [ DEBUG]:service: 6: 12324V in astra 19.2 si 0x7f61d80f8aa0 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.703 [ DEBUG]:service: 5: 12324V in astra 19.2 si 0x7f61d8065a50 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.703 [ DEBUG]:service: 3: 12324V in astra 19.2 si 0x7f61d815e2c0 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.703 [ DEBUG]:service: 2: 12324V in astra 19.2 si 0x7f61d8092d40 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.703 [ DEBUG]:service: 4: 12324V in astra 19.2 si 0x7f61d8038980 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:20.703 [ TRACE]:service: will start new instance 3 2017-03-30 16:16:20.703 [ TRACE]:service: starting 12324V in astra 19.2 2017-03-30 16:16:20.703 [ INFO]:mpegts: 12324V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 2017-03-30 16:16:20.745 [ TRACE]:subscription: 0408: linking sub 0x7f61d808d6f0 to svc 0x7f61d81523a0 type 1 2017-03-30 16:16:20.745 [ INFO]:subscription: 0408: "scan" subscribing to mux "12324V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:20.745 [ TRACE]:subscription: 0408: chain 01: input 2017-03-30 16:16:20.745 [ TRACE]:subscription: 0408: chain 02: null input 2017-03-30 16:16:20.745 [ TRACE]:subscription: 0409: creating subscription for service 10979V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:20.745 [ TRACE]:subscription: 0409: find instance for 10979V in astra 19.2 weight 2 2017-03-30 16:16:20.745 [ DEBUG]:service: 33: 10979V in astra 19.2 si 0x7f61d80935c0 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.745 [ DEBUG]:service: 8: 10979V in astra 19.2 si 0x7f61d8003930 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.745 [ DEBUG]:service: 7: 10979V in astra 19.2 si 0x7f61d8119200 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.745 [ DEBUG]:service: 6: 10979V in astra 19.2 si 0x7f61d812f250 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.745 [ DEBUG]:service: 5: 10979V in astra 19.2 si 0x7f61d80dd490 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.745 [ DEBUG]:service: 3: 10979V in astra 19.2 si 0x7f61d8002800 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.745 [ DEBUG]:service: 2: 10979V in astra 19.2 si 0x7f61d8111b70 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.745 [ DEBUG]:service: 4: 10979V in astra 19.2 si 0x7f61d8005c10 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:20.745 [ TRACE]:service: will start new instance 5 2017-03-30 16:16:20.745 [ TRACE]:service: starting 10979V in astra 19.2 2017-03-30 16:16:20.745 [ INFO]:mpegts: 10979V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 2017-03-30 16:16:20.882 [ TRACE]:subscription: 0409: linking sub 0x7f61d80079b0 to svc 0x7f61d80b9890 type 1 2017-03-30 16:16:20.882 [ INFO]:subscription: 0409: "scan" subscribing to mux "10979V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:20.882 [ TRACE]:subscription: 0409: chain 01: input 2017-03-30 16:16:20.882 [ TRACE]:subscription: 0409: chain 02: null input 2017-03-30 16:16:20.882 [ TRACE]:subscription: 040A: creating subscription for service 11685.5V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:20.882 [ TRACE]:subscription: 040A: find instance for 11685.5V in astra 19.2 weight 2 2017-03-30 16:16:20.882 [ DEBUG]:service: 33: 11685.5V in astra 19.2 si 0x7f61d8034990 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 8: 11685.5V in astra 19.2 si 0x7f61d8066af0 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 7: 11685.5V in astra 19.2 si 0x7f61d800ac20 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 6: 11685.5V in astra 19.2 si 0x7f61d80f3e00 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 5: 11685.5V in astra 19.2 si 0x7f61d80017a0 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 3: 11685.5V in astra 19.2 si 0x7f61d80f2e00 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 2: 11685.5V in astra 19.2 si 0x7f61d80b6550 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 4: 11685.5V in astra 19.2 si 0x7f61d8002ba0 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:20.882 [ TRACE]:service: will start new instance 6 2017-03-30 16:16:20.882 [ TRACE]:service: starting 11685.5V in astra 19.2 2017-03-30 16:16:20.882 [ INFO]:mpegts: 11685.5V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 2017-03-30 16:16:20.882 [ TRACE]:subscription: 040A: linking sub 0x7f61d8164300 to svc 0x7f61d8111f60 type 1 2017-03-30 16:16:20.882 [ INFO]:subscription: 040A: "scan" subscribing to mux "11685.5V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:20.882 [ TRACE]:subscription: 040A: chain 01: input 2017-03-30 16:16:20.882 [ TRACE]:subscription: 040A: chain 02: null input 2017-03-30 16:16:20.882 [ TRACE]:subscription: 040B: creating subscription for service 10847V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:20.882 [ TRACE]:subscription: 040B: find instance for 10847V in astra 19.2 weight 2 2017-03-30 16:16:20.882 [ DEBUG]:service: 33: 10847V in astra 19.2 si 0x7f61d811e440 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 8: 10847V in astra 19.2 si 0x7f61d811e380 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 7: 10847V in astra 19.2 si 0x7f61d8006600 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 6: 10847V in astra 19.2 si 0x7f61d8006540 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 5: 10847V in astra 19.2 si 0x7f61d810d0b0 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 3: 10847V in astra 19.2 si 0x7f61d80933e0 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 2: 10847V in astra 19.2 si 0x7f61d80fa680 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.882 [ DEBUG]:service: 4: 10847V in astra 19.2 si 0x7f61d810cff0 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:20.882 [ TRACE]:service: will start new instance 7 2017-03-30 16:16:20.882 [ TRACE]:service: starting 10847V in astra 19.2 2017-03-30 16:16:20.882 [ INFO]:mpegts: 10847V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 2017-03-30 16:16:20.891 [ TRACE]:subscription: 040B: linking sub 0x7f61d8100840 to svc 0x7f61d80031f0 type 1 2017-03-30 16:16:20.891 [ INFO]:subscription: 040B: "scan" subscribing to mux "10847V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:20.891 [ TRACE]:subscription: 040B: chain 01: input 2017-03-30 16:16:20.891 [ TRACE]:subscription: 040B: chain 02: null input 2017-03-30 16:16:20.891 [ TRACE]:subscription: 040C: creating subscription for service 11067.5V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:20.891 [ TRACE]:subscription: 040C: find instance for 11067.5V in astra 19.2 weight 2 2017-03-30 16:16:20.891 [ DEBUG]:service: 33: 11067.5V in astra 19.2 si 0x7f61d8164ba0 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.891 [ DEBUG]:service: 8: 11067.5V in astra 19.2 si 0x7f61d800e180 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.891 [ DEBUG]:service: 7: 11067.5V in astra 19.2 si 0x7f61d800e0c0 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.891 [ DEBUG]:service: 6: 11067.5V in astra 19.2 si 0x7f61d81002d0 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.891 [ DEBUG]:service: 5: 11067.5V in astra 19.2 si 0x7f61d8100210 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.891 [ DEBUG]:service: 3: 11067.5V in astra 19.2 si 0x7f61d806ad60 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.891 [ DEBUG]:service: 2: 11067.5V in astra 19.2 si 0x7f61d8025c70 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.891 [ DEBUG]:service: 4: 11067.5V in astra 19.2 si 0x7f61d8145ff0 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:20.891 [ TRACE]:service: will start new instance 8 2017-03-30 16:16:20.891 [ TRACE]:service: starting 11067.5V in astra 19.2 2017-03-30 16:16:20.891 [ INFO]:mpegts: 11067.5V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 2017-03-30 16:16:20.933 [ TRACE]:subscription: 040C: linking sub 0x7f61d8145e40 to svc 0x7f61d8025880 type 1 2017-03-30 16:16:20.933 [ INFO]:subscription: 040C: "scan" subscribing to mux "11067.5V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:20.933 [ TRACE]:subscription: 040C: chain 01: input 2017-03-30 16:16:20.933 [ TRACE]:subscription: 040C: chain 02: null input 2017-03-30 16:16:20.933 [ TRACE]:subscription: 040D: creating subscription for service 11626.5V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:20.933 [ TRACE]:subscription: 040D: find instance for 11626.5V in astra 19.2 weight 2 2017-03-30 16:16:20.933 [ DEBUG]:service: 33: 11626.5V in astra 19.2 si 0x7f61d8035ac0 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:20.933 [ DEBUG]:service: 8: 11626.5V in astra 19.2 si 0x7f61d8035a00 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.933 [ DEBUG]:service: 7: 11626.5V in astra 19.2 si 0x7f61d8035940 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.933 [ DEBUG]:service: 6: 11626.5V in astra 19.2 si 0x7f61d8035880 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.933 [ DEBUG]:service: 5: 11626.5V in astra 19.2 si 0x7f61d80357c0 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.933 [ DEBUG]:service: 3: 11626.5V in astra 19.2 si 0x7f61d8017980 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.933 [ DEBUG]:service: 2: 11626.5V in astra 19.2 si 0x7f61d80fb1f0 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.933 [ DEBUG]:service: 4: 11626.5V in astra 19.2 si 0x7f61d8017a40 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:20.933 [ TRACE]:service: will start new instance 33 2017-03-30 16:16:20.933 [ TRACE]:service: starting 11626.5V in astra 19.2 2017-03-30 16:16:20.933 [ INFO]:mpegts: 11626.5V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 2017-03-30 16:16:20.942 [ TRACE]:subscription: 040D: linking sub 0x7f61d8035610 to svc 0x7f61d80fae00 type 1 2017-03-30 16:16:20.942 [ INFO]:subscription: 040D: "scan" subscribing to mux "11626.5V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:20.942 [ TRACE]:subscription: 040D: chain 01: input 2017-03-30 16:16:20.942 [ TRACE]:subscription: 040D: chain 02: null input 2017-03-30 16:16:20.942 [ TRACE]:subscription: 040E: creating subscription for service 11126.5V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:20.942 [ TRACE]:subscription: 040E: find instance for 11126.5V in astra 19.2 weight 2 2017-03-30 16:16:20.942 [ DEBUG]:service: 33: 11126.5V in astra 19.2 si 0x7f61d811a5d0 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.942 [ DEBUG]:service: 7: 11126.5V in astra 19.2 si 0x7f61d811a510 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.942 [ DEBUG]:service: 6: 11126.5V in astra 19.2 si 0x7f61d811a450 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.942 [ DEBUG]:service: 8: 11126.5V in astra 19.2 si 0x7f61d80bfb20 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.942 [ DEBUG]:service: 5: 11126.5V in astra 19.2 si 0x7f61d80bfa60 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.942 [ DEBUG]:service: 3: 11126.5V in astra 19.2 si 0x7f61d80bf8e0 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.942 [ DEBUG]:service: 2: 11126.5V in astra 19.2 si 0x7f61d8035c40 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:20.942 [ DEBUG]:service: 4: 11126.5V in astra 19.2 si 0x7f61d80bf9a0 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:20.942 [ TRACE]:subscription: 040E: "scan" unsubscribing 2017-03-30 16:16:22.265 [ DEBUG]:service: 12324V in astra 19.2: Status changed to [Demuxed packets] 2017-03-30 16:16:22.265 [ DEBUG]:service: 12324V in astra 19.2: Status changed to [Demuxed packets] [Reassembled packets] 2017-03-30 16:16:22.278 [ DEBUG]:service: 12480V in astra 19.2: Status changed to [Demuxed packets] 2017-03-30 16:16:22.278 [ DEBUG]:service: 12480V in astra 19.2: Status changed to [Demuxed packets] [Reassembled packets] 2017-03-30 16:16:26.720 [ INFO]:mpegts: 12324V in astra 19.2 scan complete 2017-03-30 16:16:26.720 [ INFO]:subscription: 0408: "scan" unsubscribing 2017-03-30 16:16:30.885 [ DEBUG]:service: 11685.5V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:30.885 [ INFO]:mpegts: 11685.5V in astra 19.2 - scan no data, failed 2017-03-30 16:16:30.885 [ INFO]:subscription: 040A: "scan" unsubscribing 2017-03-30 16:16:30.885 [ DEBUG]:service: 10979V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:30.885 [ INFO]:mpegts: 10979V in astra 19.2 - scan no data, failed 2017-03-30 16:16:30.885 [ INFO]:subscription: 0409: "scan" unsubscribing 2017-03-30 16:16:30.912 [ DEBUG]:service: 11626.5V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:30.912 [ INFO]:mpegts: 11626.5V in astra 19.2 - scan no data, failed 2017-03-30 16:16:30.912 [ INFO]:subscription: 040D: "scan" unsubscribing 2017-03-30 16:16:30.912 [ DEBUG]:service: 11067.5V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:30.912 [ INFO]:mpegts: 11067.5V in astra 19.2 - scan no data, failed 2017-03-30 16:16:30.912 [ INFO]:subscription: 040C: "scan" unsubscribing 2017-03-30 16:16:30.912 [ DEBUG]:service: 10847V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:30.912 [ INFO]:mpegts: 10847V in astra 19.2 - scan no data, failed 2017-03-30 16:16:30.912 [ INFO]:subscription: 040B: "scan" unsubscribing 2017-03-30 16:16:34.878 [ INFO]:mpegts: 12480V in astra 19.2 scan complete 2017-03-30 16:16:34.878 [ INFO]:subscription: 0407: "scan" unsubscribing 2017-03-30 16:16:44.824 [ TRACE]:subscription: 040F: creating subscription for service 11126.5V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:44.824 [ TRACE]:subscription: 040F: find instance for 11126.5V in astra 19.2 weight 2 2017-03-30 16:16:44.824 [ DEBUG]:service: 33: 11126.5V in astra 19.2 si 0x7f61d8092d40 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.824 [ DEBUG]:service: 7: 11126.5V in astra 19.2 si 0x7f61d811d210 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.824 [ DEBUG]:service: 6: 11126.5V in astra 19.2 si 0x7f61d815e2c0 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.824 [ DEBUG]:service: 8: 11126.5V in astra 19.2 si 0x7f61d8009dc0 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.824 [ DEBUG]:service: 5: 11126.5V in astra 19.2 si 0x7f61d8065a50 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.824 [ DEBUG]:service: 3: 11126.5V in astra 19.2 si 0x7f61d8038980 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.824 [ DEBUG]:service: 2: 11126.5V in astra 19.2 si 0x7f61d801ac70 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.824 [ DEBUG]:service: 4: 11126.5V in astra 19.2 si 0x7f61d811db50 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:44.824 [ TRACE]:service: will start new instance 2 2017-03-30 16:16:44.824 [ TRACE]:service: starting 11126.5V in astra 19.2 2017-03-30 16:16:44.824 [ INFO]:mpegts: 11126.5V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 2017-03-30 16:16:44.865 [ TRACE]:subscription: 040F: linking sub 0x7f61d808d6f0 to svc 0x7f61d81523a0 type 1 2017-03-30 16:16:44.865 [ INFO]:subscription: 040F: "scan" subscribing to mux "11126.5V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:44.865 [ TRACE]:subscription: 040F: chain 01: input 2017-03-30 16:16:44.865 [ TRACE]:subscription: 040F: chain 02: null input 2017-03-30 16:16:44.865 [ TRACE]:subscription: 0410: creating subscription for service 12090V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:44.865 [ TRACE]:subscription: 0410: find instance for 12090V in astra 19.2 weight 2 2017-03-30 16:16:44.865 [ DEBUG]:service: 33: 12090V in astra 19.2 si 0x7f61d80dd490 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.865 [ DEBUG]:service: 8: 12090V in astra 19.2 si 0x7f61d812f250 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.865 [ DEBUG]:service: 7: 12090V in astra 19.2 si 0x7f61d8119200 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.865 [ DEBUG]:service: 6: 12090V in astra 19.2 si 0x7f61d8003930 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.865 [ DEBUG]:service: 5: 12090V in astra 19.2 si 0x7f61d80935c0 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.865 [ DEBUG]:service: 3: 12090V in astra 19.2 si 0x7f61d80b6550 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.865 [ DEBUG]:service: 2: 12090V in astra 19.2 si 0x7f61d80f2e00 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:44.865 [ DEBUG]:service: 4: 12090V in astra 19.2 si 0x7f61d8065530 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:44.865 [ TRACE]:service: will start new instance 3 2017-03-30 16:16:44.865 [ TRACE]:service: starting 12090V in astra 19.2 2017-03-30 16:16:44.865 [ INFO]:mpegts: 12090V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 2017-03-30 16:16:44.915 [ TRACE]:subscription: 0410: linking sub 0x7f61d801b0a0 to svc 0x7f61d8111f60 type 1 2017-03-30 16:16:44.915 [ INFO]:subscription: 0410: "scan" subscribing to mux "12090V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:44.915 [ TRACE]:subscription: 0410: chain 01: input 2017-03-30 16:16:44.915 [ TRACE]:subscription: 0410: chain 02: null input 2017-03-30 16:16:44.915 [ TRACE]:subscription: 0411: creating subscription for service 12728.5V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:44.915 [ TRACE]:subscription: 0411: find instance for 12728.5V in astra 19.2 weight 2 2017-03-30 16:16:44.915 [ DEBUG]:service: 33: 12728.5V in astra 19.2 si 0x7f61d800b5e0 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.915 [ DEBUG]:service: 8: 12728.5V in astra 19.2 si 0x7f61d8035e90 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.915 [ DEBUG]:service: 7: 12728.5V in astra 19.2 si 0x7f61d81648e0 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.915 [ DEBUG]:service: 6: 12728.5V in astra 19.2 si 0x7f61d80069b0 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.915 [ DEBUG]:service: 5: 12728.5V in astra 19.2 si 0x7f61d80b7e40 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.915 [ DEBUG]:service: 3: 12728.5V in astra 19.2 si 0x7f61d80fa680 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:44.915 [ DEBUG]:service: 2: 12728.5V in astra 19.2 si 0x7f61d800bce0 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:44.915 [ DEBUG]:service: 4: 12728.5V in astra 19.2 si 0x7f61d8165430 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:44.915 [ TRACE]:service: will start new instance 5 2017-03-30 16:16:44.915 [ TRACE]:service: starting 12728.5V in astra 19.2 2017-03-30 16:16:44.915 [ INFO]:mpegts: 12728.5V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 2017-03-30 16:16:44.936 [ TRACE]:subscription: 0411: linking sub 0x7f61d8164300 to svc 0x7f61d80b9890 type 1 2017-03-30 16:16:44.936 [ INFO]:subscription: 0411: "scan" subscribing to mux "12728.5V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:44.936 [ TRACE]:subscription: 0411: chain 01: input 2017-03-30 16:16:44.936 [ TRACE]:subscription: 0411: chain 02: null input 2017-03-30 16:16:44.936 [ TRACE]:subscription: 0412: creating subscription for service 11097V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:44.936 [ TRACE]:subscription: 0412: find instance for 11097V in astra 19.2 weight 2 2017-03-30 16:16:44.936 [ DEBUG]:service: 33: 11097V in astra 19.2 si 0x7f61d8002ba0 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.936 [ DEBUG]:service: 8: 11097V in astra 19.2 si 0x7f61d80017a0 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.936 [ DEBUG]:service: 7: 11097V in astra 19.2 si 0x7f61d80f3e00 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.936 [ DEBUG]:service: 6: 11097V in astra 19.2 si 0x7f61d800ac20 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:44.936 [ DEBUG]:service: 5: 11097V in astra 19.2 si 0x7f61d806dec0 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:44.936 [ DEBUG]:service: 3: 11097V in astra 19.2 si 0x7f61d8066af0 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:44.936 [ DEBUG]:service: 2: 11097V in astra 19.2 si 0x7f61d8032280 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:44.936 [ DEBUG]:service: 4: 11097V in astra 19.2 si 0x7f61d8005c10 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:44.936 [ TRACE]:service: will start new instance 6 2017-03-30 16:16:44.936 [ TRACE]:service: starting 11097V in astra 19.2 2017-03-30 16:16:44.936 [ INFO]:mpegts: 11097V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0412: linking sub 0x7f61d80079b0 to svc 0x7f61d80031f0 type 1 2017-03-30 16:16:45.070 [ INFO]:subscription: 0412: "scan" subscribing to mux "11097V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0412: chain 01: input 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0412: chain 02: null input 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0413: creating subscription for service 11435.5V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0413: find instance for 11435.5V in astra 19.2 weight 2 2017-03-30 16:16:45.070 [ DEBUG]:service: 33: 11435.5V in astra 19.2 si 0x7f61d8100210 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 7: 11435.5V in astra 19.2 si 0x7f61d800e180 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 8: 11435.5V in astra 19.2 si 0x7f61d8017a40 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 6: 11435.5V in astra 19.2 si 0x7f61d800e0c0 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 5: 11435.5V in astra 19.2 si 0x7f61d8017980 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 3: 11435.5V in astra 19.2 si 0x7f61d8092550 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 2: 11435.5V in astra 19.2 si 0x7f61d8034960 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 4: 11435.5V in astra 19.2 si 0x7f61d80933e0 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:45.070 [ TRACE]:service: will start new instance 8 2017-03-30 16:16:45.070 [ TRACE]:service: starting 11435.5V in astra 19.2 2017-03-30 16:16:45.070 [ INFO]:mpegts: 11435.5V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0413: linking sub 0x7f61d8100840 to svc 0x7f61d8004490 type 1 2017-03-30 16:16:45.070 [ INFO]:subscription: 0413: "scan" subscribing to mux "11435.5V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0413: chain 01: input 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0413: chain 02: null input 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0414: creating subscription for service 11258.5V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0414: find instance for 11258.5V in astra 19.2 weight 2 2017-03-30 16:16:45.070 [ DEBUG]:service: 33: 11258.5V in astra 19.2 si 0x7f61d806aca0 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 7: 11258.5V in astra 19.2 si 0x7f61d810cff0 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 8: 11258.5V in astra 19.2 si 0x7f61d810d0b0 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 6: 11258.5V in astra 19.2 si 0x7f61d8006600 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 5: 11258.5V in astra 19.2 si 0x7f61d8006540 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 3: 11258.5V in astra 19.2 si 0x7f61d811e380 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 2: 11258.5V in astra 19.2 si 0x7f61d8025c70 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 4: 11258.5V in astra 19.2 si 0x7f61d811e440 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:45.070 [ TRACE]:service: will start new instance 7 2017-03-30 16:16:45.070 [ TRACE]:service: starting 11258.5V in astra 19.2 2017-03-30 16:16:45.070 [ INFO]:mpegts: 11258.5V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0414: linking sub 0x7f61d8005780 to svc 0x7f61d8025880 type 1 2017-03-30 16:16:45.070 [ INFO]:subscription: 0414: "scan" subscribing to mux "11258.5V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0414: chain 01: input 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0414: chain 02: null input 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0415: creating subscription for service 11288V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0415: find instance for 11288V in astra 19.2 weight 2 2017-03-30 16:16:45.070 [ DEBUG]:service: 33: 11288V in astra 19.2 si 0x7f61d8145f00 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 0 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 7: 11288V in astra 19.2 si 0x7f61d8145e40 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 6: 11288V in astra 19.2 si 0x7f61d8002980 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 8: 11288V in astra 19.2 si 0x7f61d80028c0 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 5: 11288V in astra 19.2 si 0x7f61d8002800 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 3: 11288V in astra 19.2 si 0x7f61d8164ba0 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 2: 11288V in astra 19.2 si 0x7f61d80fb1f0 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 4: 11288V in astra 19.2 si 0x7f61d8164c60 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:45.070 [ TRACE]:service: will start new instance 33 2017-03-30 16:16:45.070 [ TRACE]:service: starting 11288V in astra 19.2 2017-03-30 16:16:45.070 [ INFO]:mpegts: 11288V in astra 19.2 - tuning on TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0415: linking sub 0x7f61d80a97b0 to svc 0x7f61d80fae00 type 1 2017-03-30 16:16:45.070 [ INFO]:subscription: 0415: "scan" subscribing to mux "11288V", weight: 2, adapter: "TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0", network: "astra 19.2", service: "Raw PID Subscription" 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0415: chain 01: input 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0415: chain 02: null input 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0416: creating subscription for service 11038V in astra 19.2 weight 2 using profile <none> 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0416: find instance for 11038V in astra 19.2 weight 2 2017-03-30 16:16:45.070 [ DEBUG]:service: 33: 11038V in astra 19.2 si 0x7f61d8035b80 TurboSight TBS 6909 DVB-S/S2 #0 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 7: 11038V in astra 19.2 si 0x7f61d8035ac0 TurboSight TBS 6909 DVB-S/S2 #10 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 6: 11038V in astra 19.2 si 0x7f61d8035a00 TurboSight TBS 6909 DVB-S/S2 #11 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 5: 11038V in astra 19.2 si 0x7f61d8035940 TurboSight TBS 6909 DVB-S/S2 #12 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 3: 11038V in astra 19.2 si 0x7f61d80357c0 TurboSight TBS 6909 DVB-S/S2 #14 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 2: 11038V in astra 19.2 si 0x7f61d8110e30 TurboSight TBS 6909 DVB-S/S2 #15 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 8: 11038V in astra 19.2 si 0x7f61d8110980 TurboSight TBS 6909 DVB-S/S2 #9 : DVB-S #0 weight 2 prio 310 error 0 2017-03-30 16:16:45.070 [ DEBUG]:service: 4: 11038V in astra 19.2 si 0x7f61d8035880 TurboSight TBS 6909 DVB-S/S2 #13 : DVB-S #0 weight 100 prio 310 error 0 2017-03-30 16:16:45.070 [ TRACE]:subscription: 0416: "scan" unsubscribing 2017-03-30 16:16:46.368 [ DEBUG]:service: 12090V in astra 19.2: Status changed to [Demuxed packets] 2017-03-30 16:16:46.368 [ DEBUG]:service: 12090V in astra 19.2: Status changed to [Demuxed packets] [Reassembled packets] 2017-03-30 16:16:46.386 [ DEBUG]:service: 12728.5V in astra 19.2: Status changed to [Demuxed packets] 2017-03-30 16:16:46.386 [ DEBUG]:service: 12728.5V in astra 19.2: Status changed to [Demuxed packets] [Reassembled packets] 2017-03-30 16:16:48.017 [ INFO]:mpegts: 12728.5V in astra 19.2 scan complete 2017-03-30 16:16:48.017 [ INFO]:subscription: 0411: "scan" unsubscribing 2017-03-30 16:16:48.208 [ INFO]:mpegts: 12090V in astra 19.2 scan complete 2017-03-30 16:16:48.208 [ INFO]:subscription: 0410: "scan" unsubscribing 2017-03-30 16:16:54.825 [ DEBUG]:service: 11126.5V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:54.825 [ INFO]:mpegts: 11126.5V in astra 19.2 - scan no data, failed 2017-03-30 16:16:54.825 [ INFO]:subscription: 040F: "scan" unsubscribing 2017-03-30 16:16:55.040 [ DEBUG]:service: 11288V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:55.040 [ INFO]:mpegts: 11288V in astra 19.2 - scan no data, failed 2017-03-30 16:16:55.040 [ INFO]:subscription: 0415: "scan" unsubscribing 2017-03-30 16:16:55.040 [ DEBUG]:service: 11258.5V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:55.040 [ INFO]:mpegts: 11258.5V in astra 19.2 - scan no data, failed 2017-03-30 16:16:55.040 [ INFO]:subscription: 0414: "scan" unsubscribing 2017-03-30 16:16:55.040 [ DEBUG]:service: 11435.5V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:55.040 [ INFO]:mpegts: 11435.5V in astra 19.2 - scan no data, failed 2017-03-30 16:16:55.040 [ INFO]:subscription: 0413: "scan" unsubscribing 2017-03-30 16:16:55.040 [ DEBUG]:service: 11097V in astra 19.2: Status changed to [Graceperiod expired] [Data timeout] 2017-03-30 16:16:55.040 [ INFO]:mpegts: 11097V in astra 19.2 - scan no data, failed 2017-03-30 16:16:55.040 [ INFO]:subscription: 0412: "scan" unsubscribing

(this will never stop)

Updated by Jaroslav Kysela over 7 years ago

Status changed from New to Fixed
% Done changed from 0 to 100

Applied in changeset commit:tvheadend|b142383a7cf51180e00ebb1c13205c14d24338dc.

Updated by Jaroslav Kysela over 7 years ago

Try v4.1-2493-gb142383 .

Updated by ian stuart over 7 years ago

Jaroslav Kysela wrote:

Try v4.1-2493-gb142383 .

Works for me ! Thanks !

Updated by C K over 7 years ago

Okay, it seems that this soulution works only for multiple services per channel. I disabled "Continue even if descrambling fails" and tried to switch to a scrambled channel.

Within a few seconds, TVH iterates through all 8 SAT>IP Tuners and tried to descramble the channel. Oscam responds the key (Oscam WebUI and THV Status Tab) but TVH continued to loop over all Tuners. Kodi resonded after each loop that the channel is scrambled.

I enabled the "Continue even if descrambling fails" checkbox and everythin worked fine. Maybe I misunderstood this option :-)

Updated by Hanspeter Müller over 7 years ago

This broke descrambling on all channels (DVB-C with one DVB-API Oscam), getting "Scrambled Channel" in Kodi, no matter if "Continue even if descrambling fails" is on or off on the htsp profile. Also seeing the cycling-though-all-tuners that C K reported...

Apr 1 13:14:47 skynet tvheadend³⁰⁹⁵: subscription: 02C0: service instance is bad, reason: No access
Apr 1 13:14:47 skynet tvheadend³⁰⁹⁵: mpegts: 530MHz in UPC Cablecom - tuning on DVB-C #2
Apr 1 13:14:47 skynet tvheadend³⁰⁹⁵: capmt: CI: Starting CAPMT server for service "N24 HD" on adapter 3

git revert b142383a7cf51180e00ebb1c13205c14d24338dc "fixed" it...

/hp

Updated by Hanspeter Müller over 7 years ago

Very wheird, i've just installed the same version, but accidentally used the clean git version, not the one where i reverted the git commit, but it still works. So, no problem anymore...

/hp

Updated by ian stuart over 7 years ago

It's fixed for me, but with one observation.

I have 8 tuners on my DVB-S and Tvheadend iterates all tuners before switching to the next service.

It should switch to the next service after failing on one tuner, no need to try with all others tuners (take some time for nothing)

#10

Updated by Thorsten Krohn over 7 years ago

File trace_with_continious_descrambling.txt trace_with_continious_descrambling.txt added
File trace_without_continious_descrambling.txt trace_without_continious_descrambling.txt added

I have the same problem here. After changeset b142383a7cf51180e00ebb1c13205c14d24338dc no channel are decoded anymore.

If i i have the continious-scramble option in the stream-settings enablebed than it works, but then if scrambled failed, the service stays still on the same service, no alternative service will used.

Attached are the traces for starting service with and without continious-scrambled-option.

Kroki

#11

Updated by Jaroslav Kysela over 7 years ago

Guys, could you test latest v4.1-2509-gfc47fce? I added the CA decision timeout and possibility to mark all service instances for all tuners with the error flag when an error occurs. Note that both behaviours (iterate through all service instance on error and skip to the next service) are correct in my eyes - when one tuner is faulty, the first (old) behaviour makes sense.

#12

Updated by Thorsten Krohn over 7 years ago

File trace_with_change_service_set.txt trace_with_change_service_set.txt added

Ok, with the new version the first problem works now: Descrambling of service are now ok.

Nut switching to alternative service dosn't work. I have for RTL two services, one oon Astra (CAID 1830) and one on cable (CAID 0B00). Both services ar working if i start them from the service-tab.

I set the option 'switch to another service' and then start the service from the channel-tab. Priority has the sat-tuner, so the service starts on sat and works, then i witched off the card for CAID 1830. But it still stays on the sat tuner. Also if i start with CAID 1830 disabled the service stays on the sat-tuner, no switch to other network/tuner.

Trace attached.

Kroki

#13

Updated by Jaroslav Kysela over 7 years ago

Do you have turned off 'Continue even if descrambling fails' in the used streaming profile?

#14

Updated by Thorsten Krohn over 7 years ago

Yes, same behaviour with option set or not set. If option set, i think it's should be correct, that the service will not change. That's for activating cards ok.

The trace is made without option set.

Did you need additional traces ...?

Kroki

#15

Updated by Jaroslav Kysela over 7 years ago

Oops. There was wrong code in the CA timeout condition - try v4.1-2513-gde71263 .

#16

Updated by Thorsten Krohn over 7 years ago

First test ... nothing changed, same behaviour ...

I will check later on and provide a trace.

Kroki

#17

Updated by Jaroslav Kysela over 7 years ago

I fixed another bug in v4.1-2515-gd8164c0, but it won't probably change the default behaviour.

#18

Updated by Thorsten Krohn over 7 years ago

File trace_service_change_on descramble_fail_.txt trace_service_change_on descramble_fail_.txt added

No changes .... only the log output

Trace attached ...

Kroki

#19

Updated by Jaroslav Kysela over 7 years ago

I think that we're close. Try v4.1-2517-ge888e4e .

#20

Updated by Thorsten Krohn over 7 years ago

File trace_service_change_on descramble_fail_1.txt trace_service_change_on descramble_fail_1.txt added

...hmmm that looks not better.

#21

Updated by Jaroslav Kysela over 7 years ago

One little change: v4.1-2518-g8069852 .

#22

Updated by Thorsten Krohn over 7 years ago

File trace_service_change_on descramble_fail_2.txt trace_service_change_on descramble_fail_2.txt added

.... same behaviour like before, i think.

#23

Updated by Jaroslav Kysela over 7 years ago

It seems that you run old binary or the 'Continue even if descrambling fails' is off. There should be [CA check] in the 'Status changed to' log lines.

#24

Updated by Thorsten Krohn over 7 years ago

Ok you are right. The 'Continue even if descrambling fails' is off. But i thought it should be off .... A quick test with option enabled also dosn't work.
But now is here prime-time and my wife will watch tv ... so i will continue testing tomorrow morning.

... and i always checkout the last revision from git.

Kroki

#25

Updated by Thorsten Krohn over 7 years ago

File trace_service_change_on descramble_fail_3.txt trace_service_change_on descramble_fail_3.txt added

... here are a quick trace, now with [CA check]

#26

Updated by Jaroslav Kysela over 7 years ago

Sorry. Blame me. I just inverted one condition. Please, try v4.1-2520-geb3e25f and keep/set 'Continue even if descrambling fails' to off (as it should be).

#27

Updated by ian stuart over 7 years ago

File trace01.txt trace01.txt added

Jaroslav Kysela wrote:

Sorry. Blame me. I just inverted one condition. Please, try v4.1-2520-geb3e25f and keep/set 'Continue even if descrambling fails' to off (as it should be).

Just tested the last build (on doozer, i hope it's really the last build).
It don't works for me.
(I have checked "Switch to another service" and unchecked "Continue even...")

It just switch between TBS tuners (slowly) and produce a lot of streams error.

If you need to test on my linux server i can give to you access (may be better for testing a fix)

#28

Updated by Thorsten Krohn over 7 years ago

File trace_service_change_on_descramble_fail_4.txt trace_service_change_on_descramble_fail_4.txt added

We are slowly getting closer ...

Now the check seems to work, and first all available tuner on sat will be checked and then are switched to the cable service.

Is it possible to switch direct to the alternative service , without checking the other tuners ? ... Then it's almost perfect.

I'm thinking if it also make sense to switch direct to the alternative channel if tuning fails. If a sat servive fails tuning on one tuner it is probably that it can not tune on the other sat tuners (thunderstorm, service deleted) ... So an option for controlling this behaviour make sense.

Attached last log

Kroki

#29

Updated by Jaroslav Kysela over 7 years ago

v4.1-2521-ga714655 ?

#30

Updated by Thorsten Krohn over 7 years ago

... now it works :-) I will test tomorrow a little bit deeper.

Quick test look realy good: When in working stream the descrambling fails .. short break an than service switches to cable tuner.

Great work ... and many thanks for spending your time for such 'nice to have feature'.

Best Kroki

#31

Updated by ian stuart over 7 years ago

Yes seem much better.

Just one thing, i don't know if it's a normal behaviour...

With "Preferred service video type:" set on HD, tvheadend don't switch to another service (i don't know if the others services are HD or SD).
If i set Preferred (...) to None, it work very well...

I confirm we are getting closer !

#32

Updated by Jaroslav Kysela over 7 years ago

Last comment - could you try v4.1-2523-gd763ef9 ?

#33

Updated by ian stuart over 7 years ago

Jaroslav Kysela wrote:

Last comment - could you try v4.1-2523-gd763ef9 ?

Look good for me. Thanks a lot Jaroslav !

Also available in: Atom PDF

Project

General

Profile

Tvheadend

Issues

Custom queries

Bug #4303

Tvheadend don't switch to the next service when descrambling fail

History

Updated by Jaroslav Kysela over 7 years ago

Updated by ian stuart over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by ian stuart over 7 years ago

Updated by C K over 7 years ago

Updated by Hanspeter Müller over 7 years ago

Updated by Hanspeter Müller over 7 years ago

Updated by ian stuart over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by ian stuart over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by Thorsten Krohn over 7 years ago

Updated by ian stuart over 7 years ago

Updated by Jaroslav Kysela over 7 years ago

Updated by ian stuart over 7 years ago