[mythtv] RFC: Better handling of time changes for a Single Recording
stuart at tase.co.uk
Wed Sep 9 16:53:59 UTC 2009
On Wednesday 09 Sep 2009 10:52:15 Matthias Dahl wrote:
> Solution 2:
> If the scheduler cannot find a listing for a scheduled recording, it looks
> in a specified time range which we could either fix (+/- 30 minutes) or
> make it optional and tunable by the user with a default of +/- xx minutes
> for each recording specified. If the scheduler finds a recording within
> that time range we record it in recordmatch but do not change the
> scheduled recording itself thus avoiding the case that several subsequent
> EPG changes could lead to overstepping of the given time buffer.
I don't have time to go into depth right now, but I've been thinking about
changing the timeslot recordings to do something like #2. We should be looking
+/- x minutes before and after the scheduled time for a match, where x is
based on the length of the program (not static or user defined).
For "single showing" recording rules we should be again looking +/- x but we
can afford to be more generous if we have the programid.
I'd agree that the current behaviour is far from ideal and suggested
workarounds are often either impractical or just not user friendly.
More information about the mythtv-dev