[mythtv] More scheduling scheduler

Paul Andreassen paulx at andreassen.com.au
Wed May 3 17:14:10 UTC 2006

On Wed, 3 May 2006 04:58 am, David Engel wrote:
> > >  It also needs to take into
> > > account whether or not softpadding has already been included.  I say
> > > maximize the softend and then give the rest to softstart.
> >
> > It only does partial padding if there isn't room between programs for
> > full padding.  Currently it proportionally allocates, with any seconds
> > truncated to minutes in favour of softend.
> Unless I misread your patch, it doesn't take into account the earlier
> recording might alreay have softend applied or the later recording
> might already have softstart applied.  If either of these are the
> case, you would be adding more pad than the user requested to one
> recording.

It removes any softpadding and then adds the the new partial softpadding.  
Work fine here.  A bit convoluted because I wanted to add the two tests.  
Could definitely be rewritten.

Now that I think about it, it doesn't take into account unset 

> > I was going to do the themes as had previously.  Will I still put
> > 'offset' in it own area?
> No, leave it the way it is in the timedate area.

Now I'm confused, will I just enlarge the "timedate" field in the themes and 
add the colour change if not full soft padding in effect?

> > Why 'Don't apply softpadding if SchedMoveHigher? isn't enabled. '  ?
> Because it makes the padding hard instead of soft.  See one of Max'
> earlier emails.

Wont it be hard only for the higher and not for same/lower priority shows.  I 
see this as expected behaviour.  If unset the high priority shows are 
guaranteed to be recorded right and the rest can fit as best they can.  The 
setHelpText should be clear enough if people read it.

We could alway change MoveHigherRecords and TryAnotherShowing to allow soft 
dropping on higher priority shows.


More information about the mythtv-dev mailing list