<div class="gmail_quote">On Thu, Mar 1, 2012 at 9:04 PM, Andrew Leech <span dir="ltr"><<a href="mailto:coronasensei@gmail.com">coronasensei@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="im">That script looks great Matt, I've wondered about stuff like this in
the past but never done anything about it.</div>
One question, when it schedules the program to allow re-record, will
that trigger the backend to try to restart the recording
immediately?<br>
<br>
I do occasionally get failed recording starting on my DVB-T cards,
and they generally just need a immediate restart to get them going.<br>
<br>
Come to think of it, I've had a few other instances lately where
recordings just finish early (as in half way through their scheduled
time), so I could modify the script to check for that too and try to
restart recording.<br>
<br>
Cheers,<br>
Andrew<br>
</div>
</blockquote></div><br><div><br></div><div>In my case, no it wouldn't restart the recordings as soon as they fail, as the failures I was testing for keep the broken recording going until the scheduled end time. The only evidence that the recording failed was the file size. I haven't been able to test other failure scenarios, but I assume that the scheduler would look for the next chance to record the entire program, rather than trying to record something already in progress.</div>
<div><br></div><div>I have heard of other people having failures that result in other small file sizes (hundreds of bytes), and this could certainly be adapted to check for those issues.</div><div><br></div><div> --Matt</div>