Re: Feature requests

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Brian wrote:
> Martin wrote:
>> I totall support your feature request.
>>
>> Regards,
>> Martin
>>
>> ------------------------------------------------------------------------
>>  > Date: Wed, 16 May 2007 20:06:35 +0300
>>  > From: pasi.juppo@xxxxxx
>>  > To: vdr@xxxxxxxxxxx
>>  > Subject:  Feature requests
>>  >
>>  > Hi,
>>  >
>>  > There are couple of annoying problems in vdr (v1.4.4 at least but most
>>  > likely also in never ones):
>>  >
>>  > 1) If there is data stream problems in a channel VDR initiates
>> emergency
>>  > exit. This can be a temporary situation and gets fixed in few
>> seconds to
>>  > minutes.
>>  >
>>  > To solve this: change to other channel and infor user via OSD
>> ("Channel
>>  > not available" or something similar)
>>  >
>>  > 2) If there is no data comming from the channel (e.g. new decrypting
>>  > card that needs to be updated first before it is ready to be used
>> or for
>>  > some reason the key is not available) VDR initiates emergency exit.
>>  > Unnecessary action and user can do shutdown action if this is really a
>>  > problem.
>>  >
>>  > To solve this: do not initiate emergency exit but show message in OSD
>>  > ("Channel not available").
>>  >
>>  > Basically every unnecessary exit should be avoided because it does not
>>  > provide any advantage to the user - just the opposite. Problems should
>>  > be informed to the user and let user decide what to do in case of long
>>  > lasting problem such as missing data stream.
>>  >
>>  >
>>  > Minor feature that would be nice:
>>  >
>>  > 3) If there is a problem like crash with VDR and a timed recording did
>>  > not get recorded VDR simply deletes the timer without notifying
>> user. Of
>>  > course the timer as such is useless but it would be nice to see that
>>  > this and this recording was not done at all, was not started in
>> time or
>>  > was not recorded fully. This way the program can be re-recorded
>> if/when
>>  > it is broadcasted again.
>>  >
>>  > And if this information can be asked from VDR then epgsearch or other
>>  > plugins can try to find missed programs again automatically.
>>  >
>>  > Br, Pasi
>>  >
>>  > _______________________________________________
>>  > vdr mailing list
>>  > vdr@xxxxxxxxxxx
>>  > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>>
>> ------------------------------------------------------------------------
>> Der kostenlose E-Mail-Dienst - schnell, einfach & sicher! Windows Live
>> Hotmail <http://mail.live.com>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> vdr mailing list
>> vdr@xxxxxxxxxxx
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
> Hi,
> 
> your point 3), I have solved that by sending myself emails from VDR when
> it starts and ends a recording. As I parse the directory name I have the
> name of the recording and its start time. End time is only valid if it
> stops recording at the correct time. Channel is missing. I send the
> emails from the BEFORE and AFTER recording calls made to my script from
> VDR. Its easy to see if something has gone wrong. BTW I put the time I
> am sending the mail in the subject of each email.
> 
> Here an example as attachment.
> 
> Maybe this could help you a little?

Nice but does not solve my "problem". When VDR misses the start and end
times of the timer it gets deleted without seeing what has been deleted.
Email solution only shows the ones that are recorded - at least partially.

Br, Pasi

_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux