<p>Handling of VDSB should be improved somehow, or at least add some configuration.</p>
<p>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.</p>
<p>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..</p>

<p>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. <br>
</p>
<div class="gmail_quote">28.4.2013 20.52 "Udo Richter" <<a href="mailto:udo_richter@gmx.de">udo_richter@gmx.de</a>> kirjoitti:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Am 28.04.2013 16:52, schrieb Brian-Imap:<br>
> So you assume it was falsely triggering a VDSB thinking 30 secs had<br>
> passed when in fact the clock probably was adjusted instead?<br>
<br>
Its the only false alarm I know of, and would be an explanation why this<br>
happens on the start of a recording. Tuning to the channel for recording<br>
may activate the clock sync for that transponder, and cause a time jump<br>
once. All other explanations involve crappy driver/hardware or bad<br>
reception.<br>
<br>
There should be a log message indicating the clock sync.<br>
<br>
Cheers,<br>
<br>
Udo<br>
<br>
<br>
_______________________________________________<br>
vdr mailing list<br>
<a href="mailto:vdr@linuxtv.org">vdr@linuxtv.org</a><br>
<a href="http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr" target="_blank">http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr</a><br>
<br>
</blockquote></div>