<div class="gmail_quote">On Mon, Apr 20, 2009 at 5:58 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>></span> wrote:<br><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">
On 04/20/2009 01:52 AM, <a href="mailto:f-myth-users@media.mit.edu" target="_blank">f-myth-users@media.mit.edu</a> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I already -said- that I manually padded -everything- to some degree.<br>
I'm saying that this solution is insufficient. To put this more clearly:<br>
</blockquote>
<br></div>
Which means /you/ agreed to all the consequences involved with overlapping start/end times. If Myth unilaterally messes with already-properly-aligned (though perhaps inaccurate) start/end times, it will cause conflicts for poor unsuspecting users who don't have as many tuners as you.<br>
</blockquote><div><br>This is a good point, but since the alternative is to add padding to every recording those poor users already have deal with conflicts on back-to-back recordings. I don't see how the proposed solution would make this situation worse.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
People are already upset enough that they have to manually do start early/end late to account for overlaps caused by some stations starting or ending a minute or two later than other stations. If Myth just adds extra time to the /displayed/ start and end times, it will upset a lot more people.<br>
</blockquote><div><br>Why? They already have to manually fix up whatever time they've added. How is it going to upset more people if Myth has added some extra time as well?<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
IMHO, the only patch that should be considered is one that stores the
runtime in the DB and displays it for the user to see when choosing
appropriate start early/end late times.<br></blockquote><br>That may well be sufficient. It'd be a good start at the very least.<br><br></div></div>Regards,<br>Steve<br>