Modify
Warning Please read the Ticket HowTo before creating or commenting on a ticket. Failure to do so may cause your ticket to be rejected or result in a slower response.

Opened 20 months ago

Closed 20 months ago

Last modified 20 months ago

#11049 closed Bug Report - General (fixed)

Maxepisodes with back-to-back recordings records one too many and expires oldest

Reported by: SiliconFiend@… Owned by: gigem
Priority: minor Milestone: 0.25.3
Component: MythTV - Scheduling Version: 0.25-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

As described on the mailing list here: http://www.mythtv.org/pipermail/mythtv-users/2012-August/338829.html

Quick summary: When recording back-to-back showings that match the same schedule which has "No. of recordings to keep" set to a non-zero value, the scheduler will record one more than the available number of "slots" for the given schedule. After the extra recording is finished, the oldest recording is expired to satisfy the Max Episodes setting. Expected behavior is simply to not record the extra show and preserve the existing recorded episodes.

Reference similar symptoms in previous bug here: http://code.mythtv.org/trac/ticket/6438

Version is v0.25.1-58-g1d41f74

Attachments (0)

Change History (5)

comment:1 Changed 20 months ago by stuartm

  • Component changed from MythTV - General to MythTV - Scheduling
  • Owner set to gigem

comment:2 Changed 20 months ago by David Engel <dengel@…>

  • Resolution set to fixed
  • Status changed from new to closed

In ae54e3b9daca3252e1319627dcedc32a5a6a9e9f/mythtv:

Fix handling of maxepisodes for babk-to-back recordings.

The logic which triggers a reschedule after the last allowed episode
starts recording was broken during a scheduler refactor.

Fixes #11049

comment:3 Changed 20 months ago by gigem

  • Milestone changed from unknown to 0.26

comment:4 Changed 20 months ago by David Engel <dengel@…>

In d51927663b67c7c035108270a31bf14aed68bcdb/mythtv:

Fix handling of maxepisodes for babk-to-back recordings.

The logic which triggers a reschedule after the last allowed episode
starts recording was broken during a scheduler refactor.

Fixes #11049
(cherry picked from commit ae54e3b9daca3252e1319627dcedc32a5a6a9e9f)

comment:5 Changed 20 months ago by wagnerrp

  • Milestone changed from 0.26 to 0.25.3

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'new'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.