<div class="gmail_quote">On Sun, Apr 12, 2009 at 4:29 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
<div>On 04/12/2009 12:07 AM, <a href="mailto:f-myth-users@media.mit.edu">f-myth-users@media.mit.edu</a> wrote: <br></div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">> I would argue that Myth should take the max of the two values and use<br>
> that in computing the endtime of the recording. (It should -not- just<br>
> use runTime! If runTime is too short, the recording will certainly be<br>
> truncated---I'd certainly rather that Myth took the maximally-conservative<br>
> approach and possibly record too much than the reverse.)<br>
><br>
<br>
</div>So, you're saying that it should ignore the starttime of the following<br>
program--so that the guy who wants to watch that show writes an e-mail<br>
to the list saying that the program was clearly listed with the proper<br>
starttime in the raw data, but for some reason, Myth changed the<br>
starttime to the incorrect starttime, so he lost the beginning of his show?<br>
</blockquote><div><br>If program A starts at 10pm and the following program B starts at 11pm but program A's runtime is supposedly 65 mins then something is clearly wrong with the schedule: either the runtime of A or the start time of B. But which? If we leave program B's start time at 11pm but change program A's end time to 11:05pm we'd be able to succesfully record either program (or both with two tuners) regardless of which piece of data was wrong.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The problem is that the entire schedule--not just the schedule for<br>
/this/ program--has to line up with endtimes matching starttimes and no<br>
gaps and ...<br>
</blockquote><div><br>Does the scheduler require that?<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">Basically, the right solution--in the face of garbage listings--is<br>
manual padding. Lesson learned... Hindsight is 20/20...<br></blockquote><br>So rather than do the best we can with the data provided we should ignore one piece of data entirely and have a blanket rule that guesses the worst case scenario?<br>
<br>Regards,<br>Steve<br></div></div><br>