Opened 14 years ago

Closed 14 years ago

#3203 closed defect (fixed)

MythTV creates duplicate recordings when end-late value is set

Reported by: anonymous Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: mythtv Version: 0.20
Severity: medium Keywords:
Cc: Ticket locked: no

Description (last modified by bjm)

I have noticed a little problem with mythtv

In Australia, all show on free to air TV start late and finish even later than scheduled. So to avoid the issue of having cut-off recordings, I have set up mythtv with 10 minutes end-late settings.

The problem with this is that whenever I press the record button (or R key), then the recording will start (e.g. display recording "xxxx") but then immediately after the channel number will show (just like I just changed channel), sound will interrupt for about .5s and it will start again. In the recordings session, I can then see two recordings "xxxx" , one lasting a few seconds, the other one being from the time I press the R key to when the recording is supposed to stop. This recording isn't marked as being currently recorded (e.g. it doesn't appear in red colour in the recording list). It does this for all channels.

If I remove the 10 minutes end-late setting back to the default 0, then the above behaviour will not happen. Note that it usually takes about 5+ minutes before the problem start disappearing (and inversely, if I change the end-late settings, it takes 5+ minutes for the problem to start appearing).

I have tried with a complete new installation of mythtv, including destroying the mysql database, and the problem always happen if I change the end-late setting.

From mythtv distribution list: "the Single record rule that needs to be created is a mismatch for the program info of the recording in progress. This somehow causes the restart then things are confused."

Change History (1)

comment:1 Changed 14 years ago by bjm

Description: modified (diff)
Resolution: fixed
Status: newclosed

SVN [13039] removes the DefaultEndOffset? minutes and I've verified that this fixes the immediate bug.

Note: See TracTickets for help on using tickets.