[mythtv-users] Inconsistent treatment of starttime/endtime vs runtime

Steve Hodge stevehodge at gmail.com
Tue Apr 21 00:55:54 UTC 2009


On Mon, Apr 20, 2009 at 5:58 PM, Michael T. Dean <mtdean at thirdcontact.com>wrote:

> On 04/20/2009 01:52 AM, f-myth-users at media.mit.edu wrote:
>
>> I already -said- that I manually padded -everything- to some degree.
>> I'm saying that this solution is insufficient.  To put this more clearly:
>>
>
> 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.
>

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.


> 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.
>

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?

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.
>

That may well be sufficient. It'd be a good start at the very least.

Regards,
Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20090421/32de0330/attachment.htm>


More information about the mythtv-users mailing list