Thank you Klaus for the Subtitles. I have been hoping for this
since I first started using vdr some years ago. (I can handle English
and German speaking films quite well, but Akira Kurosawa's masterpieces
are quite difficult without subtitles.)
Since I know you don't need the subtitles I am very g
Managed to get the PANIC again, by doing this:
- set a timer to start 1 hour from now
- close vdr
- use date to set the clock 5 min forward (with date)
- reboot
Can someone else reproduce this?
Josce
Jun 9 22:23:10 localhost vdr: [2220] VDR version 1.4.5 started
Jun 9 22:23:10 localhost vdr:
>VDR still defaults to start recordings three minutes before scheduled time,
>right? I wouldn't want to rely my recordings on a clock that is that bad.
That's why I have set it to start ten minutes earlier :)
>The worst I had was on a 286, running 40s off per day. Good thing that this
>is over.
>>Well if the PC clock was correct all the time I would probably not have
>>to use the set time function :)
>Yes, but typically PC HW clock does not drift so much. You could use
>hwclock --systohc (and possibly --utc or --localtime) after letting
>the vdr to set the system clock.
I am sure this
>However, there are some other clock-dependent things in VDR that are not
>designed to handle larger clock jumps. Usually, clock jumps should be
>just a few seconds, and only after starting VDR.
>
>You should investigate what causes the clock to jump 4 minutes. If your
>PC clock is THAT bad, its pr
Using vdr 1.4.7 is it possible to use vdr only for playing back recordings,
with xinelibout
but without a DVB receiver.
Now if I start vdr I get:
vdr: no primary device found - using first device!
and then it exits
The reason is that we will be going on a trip and my daughter would like to
ha
