[mythtv] [mythtv-commits] Ticket #3196: Autoexpire and backend fail to heed maxnewest = 0, deletes old programs that shouldn't and records new ones

Chris Pinkham cpinkham at bc2va.org
Wed Mar 14 03:37:21 UTC 2007


* On Tue Mar 13, 2007 at 11:46:46AM -0500, Tim Musa wrote:
> On 3/13/07, Chris Pinkham <cpinkham at bc2va.org> wrote:
>>* On Tue Mar 13, 2007 at 08:47:46AM -0500, Tim Musa wrote:
>>> So would this explain why I have one scheduled recording that I have
>>> set to limit to 15 shows and not to delete the old recordings, but
>>> yet Myth still deletes the old recording to record a newer show?  I
>>> have tried changing and rechanging the settings, even deleting the
>>> schedule completely and recreating it.  But Myth still deletes the
>>> old shows and records the new ones.

Actually, I have a new response to this.  Because of the existing
code, if you delete the schedule and recreate it, you could actually
end up worse.  Currently the scheduler only checks the title for a
match, so it would find 15 episodes of the same title, whereas the
recorder correctly looks at the recordid of the episodes so you
could end up somewhere in the middle of where you want to be.

If you have 3 episodes recorded from the old recordid and 12 from
the new one, with both set at maxepisodes == 15, then the expirer
would not expire any programs because you're below the 15 limit
on each recordid.

If maxnewest is not set, then the recorder would not record any
new shows.  If maxnewest was set, then the recorder would record
a new show, but the expirer would not delete any because you're
still below the maxepisodes of 15 for each recordid.  So, you'd
have 16 episodes for this title, which would be more than you
wanted.  There is no easy way around this, because of the fact
that the expirer needs to count only the episodes recorded
by that rule when looking at the maxepisodes.  You could have 2
schedules for a particular show.  One could be for new first-run
episodes with no maxepisodes set and the other could be for
syndicated reruns with a max of 5.  This is why the expirer
looks at the recordid of the shows when counting them up.  The
scheduler needs to do the same thing also in order to record
what you truly want, otherwise in the above example of 2
schedules, you could end up missing a new first-run because
the scheduler decided not to record it because you were at the
max of 5 on the rerun schedule.

The patch I attached to the ticket should fix this situation.

>>It's possible, is this a normal schedule or a power search?

> Just a normal, anytime / any channel, schedule for a particular series.

I'm not sure why this would be doing this.  It might be explained
in the backend log if you run with "-v file".

--
Chris


More information about the mythtv-dev mailing list