Recording indicator on EPG

[posi]

I use recordings often to zap channel to watch news. Thats why i put margin before recordings to 0 min. So it is 0 min also for all recordins. Now if i select several programs to record for evening, only part of the events turns to red and some stay grey.
If i select margin time other than zero, all selected events turn to red.
Is it possible to modify image so that all for recording selected events turn to red is precording time is selected to zero.

[abu baniaz]

It would have been a better representation to keep all the images separate instead of combining them on one thumbnail.

Anyway, are you sure that they are not subject to timer conflict?

[posi]

What you mean by timer conflict. With zero prerecord time the conflict should be smaller. I have tried this several times, and always the same result. Prerecord time is needed at least one min (which is minimun selectable). The epg pictures are captured from the same events (finnish epg) few minutes after each other.
Agree thumbnails. Tried to connect settings and result together.

[Orlandox]

No timer conflicts ! I have also tested it by selecting margin before recording (minutes) to 0, then that decribed above happens. When margin before recording (minutes) is set to 1 min, every event is red. I have 4 terrestial tuners.

[tappari]

In Finland programs start often late but never earlier than scheduled. That`s why prerecord-time is not needed.

[Huevos]

@posi, can you check if it is the start time, finish time or both that cause this.

[Orlandox]

EPG_rec.jpg
EPG_timers.jpg

Margin before recording (minutes) is set 0.
I can't tell if it is the start time, the lenght or the finish time. But looks like if they have the same start time, only the first is red. Posi's pics is the same.

[posi]

@posi, can you check if it is the start time, finish time or both that cause this.

If i set margin before recording to 1 and after recording to 0, each selected event turns to red. So the after recording time is not the reason.

[Huevos]

I can't reproduce this.

[littlejim]

Maybe it depends on which skin is used?

[Orlandox]

I can't reproduce this.

Definetly the problem is related to the program's start time. If they start at the same time, only the first rec is red.

[Huevos]

Definetly the problem is related to the program's start time. If they start at the same time, only the first rec is red.

So long story short, starting timers is not tread safe. e.g. if we started 2 timers at the same time the control commands would both be sent to the LNB at the same instant and therefore not be understood. This is only a problem with Unicable where multiple tuners are talking to the same LNB.

So to fix the above problem simultaneous timers are staggered by one second, i.e. if the program starts at 20:00:00 the first timer will start at 20:00:00, the next timer at 20:00:01, and the next timer at 20:00:02, and so on.

That means if you set the margin to zero the first timer background will display correctly and the subsequent ones won't.

# Only highlight timers that span an entire event

https://github.com/OpenViX/enigma2/b...stGrid.py#L541

I guess maybe we could add a margin to workaround this, e.g. here: https://github.com/OpenViX/enigma2/b...stGrid.py#L533

timer, matchType = RecordTimer.isInTimerOnService(serviceTimers, stime, duration)

Change to:

timer, matchType = RecordTimer.isInTimerOnService(serviceTimers, stime + (20 if config.recording.margin_before.value == 0 else 0), duration)

[birdman]

That means if you set the margin to zero the first timer background will display correctly and the subsequent ones won't.

But no conflicts are reported, and all timers are actually set (according to the OP).

Shouldn't the EPG just display the timers that are set and not care about anything else? Why would that code be doing any conflict checking?

[posi]

pre 0 post 0. Same start time. Ok
0_0.jpg
pre 1 post 0. Same start time. Ok
1_0.jpg
pre 0 post 3. Same start time. Error
0_3.jpg
pre 0 post 3. Different start time. Ok
0_3b.jpg
Note. If the post time is zero, still there is a mark on the following event.
Skin Simple Ten Eighty

[Huevos]

Why would that code be doing any conflict checking?

My comments have nothing to do with conflict checking, and I don't mention it. Please re-read.