[AutoTimer] End time / Start time "overlap" causes conflicts

[wedebe]

With a single tuner, a timer which ends at 1800 will cause a conflict for a timer which begins at 1800, as they are seen as overlapping.

May I suggest that end times be set to a number of seconds before (in this case, something like 17:59:50). This would also allow some time for the box to stop recording and switch channels before starting to record again.

Zap timers perhaps would start within this gap, for example at 17:59:55. So in a situation where AutoTimer adds timers while the user is away, recordings will always happen (or at least, happen more often).

The UI would always show such times rounded upwards.

Setting "guess start/end time" has its own issues.

[AbuBaniaz]

See here:
#175 (comment)
OpenPLi/enigma2-plugins@6798f07

Maybe @jbleyel can add this?

[Huevos]

???
I merged that 4 years ago.
04ecb2c

[Grumpy-Geoff]

With a single tuner, a timer which ends at 1800 will cause a conflict for a timer which begins at 1800, as they are seen as overlapping.

The second timer actually begins at 17:59:40 as the timer preparation time is 20 seconds prior to recording start, and prepare time is when the tuner is allocated (and free space checked, recording file allocated, trashes cleaned if needed).

[jbleyel]

The margin_before and margin_after needs to be 0 and the autotimer entry offset needs to be 0 for this hack.

default for config.recording.margin_before = 3
default for config.recording.margin_after = 5