Make active EIT scan in timewindow

[warpme@…]

This patch allows to make EIT active scan working in time windowed mode. If eitCrawlIdleStart is higher than 3600sec - active EIT will switch to windowed mode where collecting starts eitCrawlIdleStart number of seconds after midnight and will go for 4h time window. 4h is hard coded as I don't want to change DB schema by introducing new setting. For eitCrawlIdleStart not higher than 3600sec patch is functionally non-destructive (execution path is practically the same). Patch is not production ready, as has hardcoded 4h scan window duration and hasn't config boundaries checking.

[mdean]

This is a dup of #5754. I still think it should be closed as wontfix. (Also a dup of #9765, but that one didn't have a patch.)

IMHO, this should be done the way Janne was planning (as obliquely referenced in ticket:5754#comment:25 ) such that it does not use any settings, but just always does the right thing. In other words, it performs an EIT scan occasionally and grabs data from all muxes then "sleeps" for a while. That "while" could even be dynamically tuned automatically by the grabber or just start out using some reasonable time for now and be extended later. (Ideally EITCrawIdleStart , without the overloaded meaning, would also be automatic.)

[warpme@…]

Mike, Thx for Your time spent on this ticket. Small remarks form my side: 1\AFAK it is not exact duplicate of 5754 & 9765 as two formers realized duty cycle for EIT while my approach realizes EIT on exact given time schedule. In other words - my patch guarantees EIT will scan only within exactly defined time window; 2\I fully share Your view about desired simplicity in myth setup - so enriching setup screens about additional settings like EITscanDuration is not obvious also for me. It will be good however to have such functionality (+ settings on DB level) for tweakers like You or me; 3\Janne suggestion is nice but IMHO orthogonal to mine as I can imagine users preferring less EIT self-inteligence for more control/predictability (i.e. BE sleeping during day and commflaging/transcoding/scanningEIT at night in time-window). Oh BTW: this patch nicely workarounds 10016 & 9480 for me. While 9480 might be 9480 former patch specific, 10016 looks like not yet widely discovered bug.

[dekarl@…]

Why do you want to make active EIT scan in timewindow?

I'm asking because I intend to unbreak idle shutdown with active EIT scan enabled. Which might make this patch unneccesary (if you want to safe power you can use idle shutdown) or neccessary (if you want to keep the guide up to date without any scheduled recording while using idle shutdown).

[warpme@…]

Karl, Honestly speaking I not need it anymore :-). I developed this patch in times when active EIT scanner causes deadlocks in BE when LiveTV is launched. Time windowed EIT scanner allowed me to minimalize such deadlocks. Fortunately - at some point in time - Daniel fixed this bug and now I have continuously running EIT scanner without negative issues with LiveTV. Speaking about this patch current usefulness: I can imagine someone wants to setup BE for kind of batch processing at night (transcodes, etc) and have it off for rest of day. In such case it might be wise to set active EIT scanner in this time window with short idle timeout setting (as this will allow to gather as much EIT data as possible in short period of time - when BE is alive). This is for sure corner and little artificial case...