[vdr] Thunderstorm over Munich
taferner at kde.org
Mon May 28 14:22:10 CEST 2007
On Monday 28 May 2007 10:38:50 Marko Myllymaa wrote:
> On Sun, 27 May 2007, Andrew Herron wrote:
> > I have to say that I agree with both of you... constructive criticism is
> > best!
> > As a quiet 'user' of vdr, for about a year, I agree with the sentiments
> > in Martin's post. It is very frustrating that vdr exits when reception is
> > less than perfect. I personally would prefer it if vdr announced on
> > screen that there was a bad signal condition. This is particularly
> > frustrating if at the time you are just watching a perfectly good
> > recording.
> I agree, with all. I would suggest to handle viewing recording or running
> a plugin (dvd plugin or mp3/mplayer etc.) would get a priority, for
> example 90. Then every recording that has lower priority would not cause
> emergency exits, no matter what. But if recording has higher priority, it
> can cause restarts.
Hmm... IMO it is good that vdr tries to fix the recording problem with a
restart. If I have the choice between a corrupted recording and being
interrupted by a restart, I would choose the restart.
However, it gets anoying when vdr restarts constantly. That is IMO what
bothers us here. So if vdr could have some sort of restart-retry timeout,
things would be better, IMO.
A solution might be to create a file like .update, e.g. /video/.restart, that
contains the timestamp of the vdr restart, when one happens. Could simply
be a file with the time_t to make things realy simple.
Vdr reads that file on its next start, seconds later, and knows that it did
try a restart. So it will not try another restart for a while.
More information about the vdr