[mythtv-commits] Ticket #1060: Backend crash/restart does not always resume interrupted (aborted) recordings
MythTV
mythtv at cvs.mythtv.org
Wed Jan 18 19:58:30 UTC 2006
#1060: Backend crash/restart does not always resume interrupted (aborted)
recordings
-------------------------------------+--------------------------------------
Reporter: justifiably at cwazy.co.uk | Owner: danielk
Type: defect | Status: closed
Priority: minor | Milestone: 0.19
Component: mythtv | Version: head
Severity: medium | Resolution: invalid
-------------------------------------+--------------------------------------
Comment (by justifiably at cwazy.co.uk):
Hmm. I'm reluctant to reopen this since I missed a nuance of the
scheduling and obviously don't understand the internals, but I just did a
couple of tests and didn't get quite the results expected:
1. Interrupt a recording with a future repeat. Partial recording gets
marked as aborted and as you suggest, future showing is lined up to be
recorded (this seems to happen after a re-run of the scheduler, when I
first looked at upcoming episodes, I saw "Aborted" followed by "Already
recorded" for the repeat). This is good.
2. Interrupt a recording without a future repeat. I set a recording "any
time on any channel" by choosing a program from the guide. Then I
restarted the backend, the recording was marked as aborted but did *not*
automatically begin recording again.
This is not so good --- I want the scheduler to continue recording this
show, and it should, shouldn't it?
In both cases the aborted recording does not inherit the default
transcode/flag setting, see #1061.
--
Ticket URL: <http://cvs.mythtv.org/trac/ticket/1060>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list