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

[MythTV]

#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.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/643>
MythTV <http://www.mythtv.org/>
MythTV