[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
Tue Mar 13 13:47:46 UTC 2007
On 3/12/07, Chris Pinkham <cpinkham at bc2va.org> wrote:
>
> We don't check maxnewest here because the expirer isn't in charge of
> what gets recorded, it just deletes the oldest (or whatever the expire
> sort order is set to). The scheduler is the one that is in charge of
> whether we record new episodes. There is a bug in the scheduler's
> maxepisodes logic, it is not checking the recordid of the rule against
> the recordid of the existing programs. maxepisodes used to look at
> the program title, now it looks at the recordid, but the scheduler was
> never changed to take this into account. I looked at this when you
> submitted your ticket and verified, but didn't make any comments about
> it, I just moved it into my view because I know what the fix is.
>
> --
> Chris
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.
Just wondering.
Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20070313/05a92329/attachment.htm
More information about the mythtv-dev
mailing list