[mythtv-users] Odd behaviour when a program is scheduled to record by two schedules at once

Nick Morrott knowledgejunkie at gmail.com
Fri Jun 20 15:39:33 UTC 2008

On 20/06/2008, Kevin Kuphal <kkuphal at gmail.com> wrote:
> On Fri, Jun 20, 2008 at 10:23 AM, Nick Morrott <knowledgejunkie at gmail.com>
> wrote:
> >
> > On 19/06/2008, David Engel <david at istwok.net> wrote:
> >
> > >  a record all on any channel rule.  In your case, both schedules are
> > >  record all on any channel so a tie breaker is used and the schedule
> > >  which was create earlier wins.  If you recreate your rules in the
> > >  opposite order, you should get what you want.
> >
> > David,
> >
> > Without seeking reprisals from the scheduling gods, could you please
> > explain why, in the case of such a tie, the overall priority does not
> > dictate which rule wins when their specificity is the same? The
> > frontend offers an easy way to view/increase/decrease priority for
> > rules, but a complicated rule could take a fair amount of effort to
> > recreate.
> How could the overall priorities be different in the case of a tie?  If the
> priorities were different, the higher priority item would win.  The only way
> you have a tie where the age of the rule comes into effect is in the case of
> identical resulting priorities on different rules.

Per the initial post, the rules would appear to have different
priorities and the /lower/ priority rule was being scheduled, hence
why I asked. David stated (I may have read more into it than he posted
though) that "When two schedules match the same program, the more
specific rule generally wins regardless of the priorities". Therefore,
if the rules have the same specificity, than the earlier rule wins and
not the rule with higher priority..

Nick Morrott

MythTV Official wiki:
MythTV users list archive:

"An investment in knowledge always pays the best interest." - Benjamin Franklin

More information about the mythtv-users mailing list