Re: Problems with VDSB, how to automate in SYSLOG

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

 



Handling of VDSB should be improved somehow, or at least add some configuration.

It's annoying if VDR is recording multiple channels, and one channel has VDSB.. emergency exit at this point will break all the other recordings, which otherwise would be fine.

Also I think VDR should try tuning to same channel with another frontend. People might have different size dishes on different tuners. Some channels might be unavailable in bad weather with small dishes, but view with larger one. VDR should try all possible methods to tune the wanted channel, before resorting to emergency exit..

Perhaps VDR should also store the time of previous emergency exit.. if VDSB continues after first emergency exit, it's not very useful to exit again. One emergency exit per recording should be enough.

28.4.2013 20.52 "Udo Richter" <udo_richter@xxxxxx> kirjoitti:
Am 28.04.2013 16:52, schrieb Brian-Imap:
> So you assume it was falsely triggering a VDSB thinking 30 secs had
> passed when in fact the clock probably was adjusted instead?

Its the only false alarm I know of, and would be an explanation why this
happens on the start of a recording. Tuning to the channel for recording
may activate the clock sync for that transponder, and cause a time jump
once. All other explanations involve crappy driver/hardware or bad
reception.

There should be a log message indicating the clock sync.

Cheers,

Udo


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

_______________________________________________
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