Terrestrial refuses to create a timer with a start time equal to an existing timers end time......
.... I'm following up abu's last post #15.
Post #17 was one off timers.
Autotimers behave differently, and are allowed to create timers which start at the same time as another timer ends.
No conflict reported.
Will it record/work? Answer at 15:00.
The answer is yes.
So autotimers can cope, but one off timers refuse to allow you to achieve effectively the same sequence of recordings.
We may have to add the fix that was applied to autotimers plugin to timer.py.Can you find the commit?
EDIT:
https://github.com/oe-alliance/enigm...ca3f1a7b728e29
Last edited by abu baniaz; 10-03-20 at 18:09.
ccs (10-03-20)
That AutoTimer.py fix appears to be in the wrong place.
An AutoTimer sets a timer by using the timer code, so if you wish to allow a recording to start at the same time as another ends the place to put it is in the timer code, not the autotimer code.
Although that's not actually what the AutoTimer code does.
It seems to be coded to only work when a timer has no margins set for before and after the actual recording?
Last edited by birdman; 10-03-20 at 19:33.
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD