Bug #2581
closed
Scan queue length does not get smaller
Added by Rob vh over 10 years ago.
Updated over 10 years ago.
Found in version:
3.9.2300, 3.9.2318
Description
Every now and then I scan for new muxes. I switch on "Idle scan" and "Network discovery" in Networks. Then "Scan Q length" field gets set to the number of Muxes in each network and scanning starts. However, since a month, the Scan Q length value does not decrease any more. It used to go down to 0, but no more.
In syslog I see that the scan seem to complete.
Files
- Status changed from New to Invalid
The idle scan repeatly continues to scan all muxes. It's not useful for standard operation as described in help. Turn off the "idle scan" in the network settings. The scan/discovery is proceed in every mux tune request (including EPG or regular streaming).
There are several muxes that I would not tune to for recording or viewing, but I am interested to find out if new services are added to those muxes. And does the normal tune operation identify new muxes? How would I find out, unless there was some automated "scan all muxes" process?
Also, may bug report is that the scan Q length counter is not maintained, and thus the field on the network display is wrong, incorrect. It used to be a very helpful field, showing when each position was scanned. So just leaving it in a half-way supported state is not good.
If idle scan is enabled, all muxes of the corresponding network are always in pending state, there is no way to set them to idle manually.
As Rob pointed out, idle scan is very usefull to catch new transponders which would need to be added manually each time something changes (if you have eg only Astra, that's not a big deal, but it makes a difference if you have a bunch of LNBs), and whats wrong about using idle resources? Bandwidth is low so that there is not even a measureable power disadvantage.
just my $.02
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 