[mythtv-users] Why does mythtv decide to postpone a recording?

Chris Pinkham cpinkham at bc2va.org
Sat Apr 14 21:54:02 UTC 2007


* On Sat Apr 14, 2007 at 02:29:57PM -0700, Marco Nelissen wrote:
> the same thing is going to happen with this week's episode of Lost: it's
> not planning to record it on the 18th, but will instead record it on the
> 25th. Here's what mythbackend --printsched had to say:

> Title - Subtitle                    Chan ChID Day Start  End   S C I  T N Pri
> Lost - "Catch-22"                     71 1071  18 22:00-23:00  1 0 0  C L   0

I think the 'C' there and the 'W' and 'C' below are the key things to notice.

> Lost - "Catch-22"                     71 1071  25 21:00-22:00  1 1 1  W 1   1
> Lost - "D.O.C."                       71 1071  25 22:00-23:00  1 1 1  C 1   0

You have 2 recording rules setup for Lost.  One appears to be a Weekslot and one
a Channel record.  The Weekslot is a +1 priority and the channel is a +0.  So,
the Weekslot next week wins over the Channel record this week.

Because you don't have data for the 2nd week out, it shows right now that it will
record "D.O.C." on the 25th, but by the time the 25th rolls around, you'll have
guide data for the next week and the scheduler will decide to record "D.O.C." in
the weekslot position the next week rather than the channel position on the 25th.

--
Chris


More information about the mythtv-users mailing list