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

Tim Musa opel1970 at gmail.com
Wed Mar 14 12:47:10 UTC 2007

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

Well, I am only getting 15 episodes of the show, so it is expiring shows
correctly to keep the right maximum.  It is just deleting the old shows
instead of not recording new ones.

Oh well.  It's no big deal.  I just thought it might tie in with this issue
being discussed.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20070314/7b482fd3/attachment.htm 

More information about the mythtv-dev mailing list