[mythtv] Re: [mythtv-commits] Ticket #643: Program matching multiple recording schedules behaves unexpectantly

Michael T. Dean mtdean at thirdcontact.com
Fri Nov 11 22:37:54 EST 2005


MythTV wrote:

>#643: Program matching multiple recording schedules behaves unexpectantly
>-------------------------------+--------------------------------------------
> Reporter:  mythtv at hburch.com  |       Owner:  ijr
>     Type:  defect             |      Status:  new
> Priority:  minor              |   Milestone:     
>Component:  mythtv             |     Version:     
> Severity:  medium             |  
>-------------------------------+--------------------------------------------
>If you create multiple recording schedules, the behavior is unexpected
> (for this user, at least).
>
> Consider two recording schedules:
> Schedule NEWEPISODES that "record new episodes only" with priority +1
> Schedule REPEATS that records all repeat episodes of show A with priority
> -1
> (REPEATS is programmed as a "Custom Record", FIRSTRUNS was added first,
> lower recordid)
>
> Episode A, a new episode, matches against NEWEPISODES and is scheduled
> with priority +1.
>
> Episode B, a repeat, matches against NEWEPISODES, but is then discarded as
> a repeat.  It is not considered as a match against REPEATS.
>
> This appears to be a problem in PruneRedundants.  Patch forthcoming.
>  
>
Actually, it seems to be by design (it's a features, not a bug).  See 
the following threads (starting with the linked posts, especially):

http://www.gossamer-threads.com/lists/mythtv/users/156126#156126 (and 
http://www.gossamer-threads.com/lists/mythtv/users/156150#156150 )

http://www.gossamer-threads.com/lists/mythtv/users/145147#145147

These threads--in addition to explaining why it was designed as 
such--explain how to properly schedule your recordings.

Mike


More information about the mythtv-dev mailing list