[mythtv] Same old mind reading crud.

Martin Long mythtv at longhome.co.uk
Wed Apr 11 20:40:41 UTC 2007

I see your point. It doesn't make a great deal of sense to tell the
tuner to pad a particular recording, but allow it to remove it in order
to resolve conflicts - either you want the padding because you expect
the show to overrun, or you don't.

I guess the reason I like this idea is because:

   1) _most_ programs in the UK seem to run to schedule - it's rare that
the padding is needed. 
   2) Some times I have a LOT of programs scheduled, and I'd rather drop
the padding (which I know I don't need 90% of the time) that have

I can see that my reasoning is probably quite personal to me, and in
fact your SchedOpenEnd commit actually does the trick for me anyway. So
if I make any changes I'll just hang on to them in my local tree. 

Thanks for you help with the code. 



On Wed, 2007-04-11 at 13:07 -0700, Bruce Markey wrote:
> Martin Long wrote:
> > Thanks Bruce for the pointers.
> > 
> > I'm sorry you feel my contribution is crud.
> I was referring to this tired old topic that has been rehashed
> for years. There is no magic solution. If the content of a
> program is expected to extend outside the listed times, then
> the scheduler needs to be told with endoffset that the highest
> priority shows must record to their conclusion. If you expect
> to require extra time to capture content for the majority of
> your rules, DefaultEndOffset can be used.
> However, If time that is anticipated to be necessary in order
> to capture content is allowed to be dropped, then the content
> of the show will be truncated. No amount of hand waving, double
> think, bait and switch or proposed mind-reading algorithms will
> change this.
> --  bjm
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

More information about the mythtv-dev mailing list