AlexWilMac
Moderator
This is a issue I've noticed for the first time under OBH 0.6 and it is still present.
I have some (repeated) timers that are set to record within a NAS folder and not into internal HDD (that is the default mapped as /media/hdd).
If, for any reasons, the NAS is not available, as soon as the timers tries to start not only it fails (as obvious) but also it modifies for its own the end time and sets it equal to the starting time. If I don't notice this fact, the next time the NAS is available, the timer simply does not work and does not record again, just because the start and the end time are now identical.
As I said, this has always occurred to me with my NAS but my suspect is it would occur also with any else storage device in case it is not available.
I have some (repeated) timers that are set to record within a NAS folder and not into internal HDD (that is the default mapped as /media/hdd).
If, for any reasons, the NAS is not available, as soon as the timers tries to start not only it fails (as obvious) but also it modifies for its own the end time and sets it equal to the starting time. If I don't notice this fact, the next time the NAS is available, the timer simply does not work and does not record again, just because the start and the end time are now identical.
As I said, this has always occurred to me with my NAS but my suspect is it would occur also with any else storage device in case it is not available.