<div class="gmail_quote">On Fri, Jan 15, 2010 at 12:12 PM, jedi <span dir="ltr"><<a href="mailto:jedi@mishnet.org">jedi@mishnet.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, Jan 15, 2010 at 11:26:41AM -0500, Eric Sharkey wrote:<br>
> On Fri, Jan 15, 2010 at 7:55 AM, Mike Dent <<a href="mailto:mcdent@gmail.com">mcdent@gmail.com</a>> wrote:<br>
> > Recently he has been noticing that some programs have been listed as<br>
> > recorded but when he goes to watch them it says something like<br>
> > "unable to find the recording".<br>
> > This problem has been intermittent.<br><br>
> It seems that sometimes mythTV just fails to get a recording when<br>
> there's some problem with the tuner (for various types of tuner) and<br>
> it just doesn't notice. It thinks it got the recording, but there's<br>
> nothing on disk when you go to play it. It happens in .21 and still<br>
> happens in .22.<br>
<br>
</div>...this seems like something that there should be more done about. I<br>
suspect that even the devs have occasions where something doesn't go<br>
quite right with the tuner and something is missed. If a recording is<br>
botched, it would be very cool if it was detected automatically (by say<br>
catching the fact that the file is 0 bytes or doesn't exist) and sorting<br>
the recorded tables out automatically rather than this being a manual<br>
process.</blockquote><div> </div><div>There is an open ticket for this issue: <span class="Apple-style-span" style="font-family: arial, sans-serif; border-collapse: collapse; color: rgb(80, 0, 80); "><a href="http://svn.mythtv.org/trac/ticket/3872">http://svn.mythtv.org/trac/ticket/3872</a></span></div>
<div><font class="Apple-style-span" color="#500050" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" color="#500050" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: arial; "><div>
This has also been discussed at length in the mailing lists and IRC channels. </div><div><font class="Apple-style-span" color="#500050" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><font class="Apple-style-span" color="#000000" face="arial"><span class="Apple-style-span" style="border-collapse: separate;"><br>
</span></font></span></font></div></span></span></font></div><div><font class="Apple-style-span" color="#500050" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">It will get fixed eventually, but is a low priority. And since there are several scenerios which can cause a zero-byte recording, the 'fix' can be just as complex. </span></font></div>
<div><font class="Apple-style-span" color="#500050" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" color="#500050" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">"Patches Welcome!" </span></font></div>
<div><font class="Apple-style-span" color="#500050" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" color="#500050" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">J-e-f-f-A</span></font></div>
</div>