[mythtv-commits] Ticket #10747: [PATCH] Autogenerate originalairdate for new episode repeats

MythTV noreply at mythtv.org
Wed May 23 11:46:41 UTC 2012


#10747: [PATCH] Autogenerate originalairdate for new episode repeats
-------------------------------------------+------------------------
     Reporter:  Bradley Baetz <bbaetz@…>   |      Owner:  stuartm
         Type:  Patch - Feature            |     Status:  new
     Priority:  minor                      |  Milestone:  unknown
    Component:  MythTV - Mythfilldatabase  |    Version:  0.25-fixes
     Severity:  medium                     |   Keywords:
Ticket locked:  0                          |
-------------------------------------------+------------------------
 Not all xmltv sources include the original airdate in the <previously-
 shown> element (mine doesn't).

 Without this, conflicts (either directly, or that could be resolved with
 the "reschedule higher priorities" option) don't cause a later repeat to
 be triggered for "new episode only" recording rules, because the second
 showing isn't marked as new in the guide data.

 The code in mythfilldatabase fixes this by changing the 'previouslyshown'
 field in the DB, but this only happens if the original airdate is within
 NewEpisodeWindow days, so without the original airdate field in the xmltv
 data that code doesn't trigger.

 However, in all the cases that this will make a difference to scheduling,
 the first showing is probably in the collected guide data anyway, so we
 can use that to set the originalairdate field.

 The attached patch sets the originalairdate if that field is not in the
 xmltv data, its a repeat showing, and there is a matching new episode in
 the program data. Its simplest to do that at the same time as first/last
 is being set (and to use the same matching rules), so I moved that code
 before the check for repeats.

 I also changed the housekeeping process to keep at least NewEpisodeWindow
 days of guide data, so that this can work (this effectively changes the
 default guide keeptime from 10 to 14 days). That may not be a good idea if
 people set that setting quite high for some reason, though.

 The same thing could presumably be done for EIT data, but I don't use
 that.

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/10747>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center


More information about the mythtv-commits mailing list