Project

General

Profile

Bug #5548

Idle scan muxes

Added by Alex Donato almost 6 years ago. Updated over 5 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-02-16
Due date:
% Done:

100%

Estimated time:
Found in version:
4.3-1733~g7d3aa1194
Affected Versions:

Description

Hi, i´ve observed, that the Option "Idle scan muxes" for Auto- IPTV- Networks does suddenly continuously scan the same mux, instead of Looping through the muxes.
This can only be interrupted by disabling "idle scan muxes", and hit "Force scan". Then it loops again through the muxes.
best alessandro

Files

mpegts.log (243 KB) mpegts.log Pablo R., 2019-03-01 10:38

History

#1

Updated by Pablo R. almost 6 years ago

I've tried it with 4 IPTV channels for an Auto IPTV Network (with 'IPTV threads' at 6, 2 and 1) and it works properly in all cases.

The scan will be limited by 'Maximum # input streams' and 'Maximum bandwidth (Kbps)'.

#2

Updated by Pablo R. almost 6 years ago

Ok, I see the problem.

By limiting the IPTV network to 1 and having several channels. As the scanned channel returns to PEND, same channel is continuously scanned without passing through the others.

#3

Updated by Pablo R. almost 6 years ago

It should stay in IDLE (after scanning) until all the scan of the network is completed, and then all back to PEND.

#4

Updated by Alex Donato almost 6 years ago

yes, you described the problem correctly. i limited parallel streams to 1 when the issue occured.

#5

Updated by Pablo R. over 5 years ago

I have verified that the same thing happens in DVB-T when you only scan with an adapter and there are more frequencies than adapters.

You never get to scan all the muxes, it always scan the same.

#6

Updated by Pablo R. over 5 years ago

I have tested with DVB-S network type and it happens the same. Each tuner, one frequency while scanning. It is definitely a bug it is impossible to idle scan all the network.

Tested with IPTV, DVB-S and DVB-T.

#7

Updated by Pablo R. over 5 years ago 

2019-03-01 10:32:22.301 [  DEBUG]:mpegts: adding mux channels.m3u - #0 in NER to scan queue weight 2 flags 2000
2019-03-01 10:32:22.301 [  DEBUG]:mpegts: adding mux channels.m3u - #VAMOS in NER to scan queue weight 2 flags 2000
2019-03-01 10:32:22.301 [  DEBUG]:mpegts: adding mux channels.m3u - #0 HD in NER to scan queue weight 2 flags 2000
2019-03-01 10:32:22.301 [  DEBUG]:mpegts: adding mux channels.m3u - #VAMOSHD in NER to scan queue weight 2 flags 2000

2019-03-01 10:32:22.301 [   INFO]:subscription: 0005: "scan" subscribing to mux "channels.m3u - #VAMOS", weight: 2, adapter: "IPTV #1", network: "NER", service: "Raw PID Subscription" 
2019-03-01 10:32:37.301 [   INFO]:mpegts: channels.m3u - #VAMOS in NER scan complete
2019-03-01 10:32:37.301 [  DEBUG]:mpegts: removing mux channels.m3u - #VAMOS in NER from scan queue
2019-03-01 10:32:37.301 [  DEBUG]:mpegts: adding mux channels.m3u - #VAMOS in NER to scan queue weight 2 flags 0000
2019-03-01 10:32:47.302 [   INFO]:subscription: 0007: "scan" subscribing to mux "channels.m3u - #VAMOS", weight: 2, adapter: "IPTV #1", network: "NER", service: "Raw PID Subscription" 
[...]
#8

Updated by Jaroslav Kysela over 5 years ago

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

Applied in changeset commit:tvheadend|717030bca5b8087d073a40f45092bc1eb7fdb8bb.

Also available in: Atom PDF