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

[f-myth-users at media.mit.edu]

    > Date: Sun, 12 Apr 2009 11:58:32 +0100
    > From: Mike Perkins <mikep at randomtraveller.org.uk>

    > Eh? Mike, I think you may have misunderstood what's going on here. I think the 
    > OP is discussing what action myth should take when presented with inconsistent 
    > scheduling data for any single program. He's not suggesting that SD move the 
    > start time of a subsequent program.

Exactly right.

    > If any user wants to record the subsequent program, as well as the one with the 
    > weird timings, then the scheduler is going to record it on a second tuner, if 
    > present, or reschedule if it can't (assuming overlap caused by padding).

Yes.

    > If any user just wants to record the second program, as you say, the start time 
    > is authoritative, so what difference does the timings of the previous program 
    > make? None. As I understand it, each recording request we make to myth is 
    > treated as a separate entity, so the timings of preceding/subsequent programs 
    > are irrelevant.

That's certainly my understanding as well.

    > If the scheduler determines that a program recording request is x minutes, 
    > however long that is, then that's the timing it should use to figure out how 
    > best to record that program. Shouldn't affect the timings of any other program 
    > at all. If x = max(duration, runtime), sounds good to me.

Yes.  That's precisely what I was trying to get across.