[vdr] Re: Problem with timer-recording

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Achim Lange wrote:
> 
> After it worked for a while pretty well, my timed recording last saturday went pretty bad. instead of recording more then 3 hours of startrek, it stopped after 2 min, which seem not to be replayable.
> 
> Has anyone got an idea what might have gone wrong?
> 
> It was programmed from 13:58 to 17:15
> 
> Here is the relevant syslog-part
> 
> Nov 24 13:52:34 stb vdr[344]: Local Time  = Sat Nov 24 13:53:19 2001  (1006606399)
> Nov 24 13:53:34 stb vdr[344]: System Time = Sat Nov 24 13:53:34 2001  (1006606414)
> Nov 24 13:53:34 stb vdr[344]: Local Time  = Sat Nov 24 13:53:27 2001  (1006606407)
> Nov 24 13:53:28 stb kernel: lirc_serial: AIEEEE: your clock just jumped backwards
> Nov 24 13:53:28 stb kernel: lirc_serial0 1 3bff9848 3bff984e 8f623 f5a8
> Nov 24 13:54:04 stb vdr[344]: System Time = Sat Nov 24 13:54:04 2001  (1006606444)
> Nov 24 13:54:04 stb vdr[344]: Local Time  = Sat Nov 24 13:54:14 2001  (1006606454)
> Nov 24 13:54:47 stb vdr[344]: System Time = Sat Nov 24 13:54:47 2001  (1006606487)
> Nov 24 13:54:47 stb vdr[344]: Local Time  = Sat Nov 24 13:58:26 2001  (1006606706)

Can you see how the system time jumps back and forward here?

> Nov 24 13:58:26 stb vdr[342]: timer 1 start
> Nov 24 13:58:26 stb vdr[342]: switching to channel 4
> Nov 24 13:58:26 stb vdr[342]: Title: 'Star Trek - Das n\xe4chste Jahrhundert' Subtitle: 'Besuch von der alten Enterprise'
> Nov 24 13:58:26 stb vdr[342]: record /video/Star_Trek_-_Das_n\xe4chste_Jahrhundert/2001-11-24.13:58.50.50.rec
> Nov 24 13:58:26 stb vdr[342]: creating directory /video/Star_Trek_-_Das_n\xe4chste_Jahrhundert
> Nov 24 13:58:26 stb vdr[342]: creating directory /video/Star_Trek_-_Das_n\xe4chste_Jahrhundert/2001-11-24.13:58.50.50.rec

Ok, it's "Nov 24 13:58", so VDR starts recording.

> Nov 24 13:58:27 stb vdr[344]: System Time = Sat Nov 24 13:58:27 2001  (1006606707)
> Nov 24 13:58:27 stb vdr[344]: Local Time  = Sat Nov 24 13:54:48 2001  (1006606488)
> Nov 24 13:54:49 stb kernel: lirc_serial: AIEEEE: your clock just jumped backwards

Woopsy-daisy - we just jumped back in time...

> Nov 24 13:54:49 stb kernel: lirc_serial0 1 3bff9899 3bff9973 5b86d 5ea0d
> Nov 24 13:54:52 stb vdr[342]: recording to '/video/Star_Trek_-_Das_n\xe4chste_Jahrhundert/2001-11-24.13:58.50.50.rec/001.vdr'
> Nov 24 13:54:52 stb vdr[812]: output thread started (pid=812)
> Nov 24 13:54:52 stb vdr[813]: input thread started (pid=813)
> Nov 24 13:54:54 stb vdr[812]: output thread ended (pid=812)
> Nov 24 13:54:54 stb vdr[813]: input thread ended (pid=813)
> Nov 24 13:54:54 stb vdr[342]: buffer stats: 21244 (2%) used
> Nov 24 13:54:54 stb vdr[342]: timer 1 stop
> Nov 24 13:54:54 stb vdr[342]: deleting timer 1

...so the timer doesn't match any more, and since it is a "one time" timer, VDR assumes
it is done.

> Nov 24 13:59:09 stb vdr[344]: System Time = Sat Nov 24 13:59:09 2001  (1006606749)
> Nov 24 13:59:09 stb vdr[344]: Local Time  = Sat Nov 24 13:59:03 2001  (1006606743)

Jumping forward in time again, but the timer is already gone...

Ok, maybe the timer mechanisms in VDR should react more flexible to time
warps, but I do believe that it is a fair assumption to expect a linear
time base. You should disable setting the system time to the transponder
time - the time from the transponders is just no good...

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
_______________________________________________________________