[mythtv-commits] Re: Ticket #430: Tuner busy on consecutive
recordings
MythTV
mythtv at cvs.mythtv.org
Sun Oct 9 19:13:02 UTC 2005
#430: Tuner busy on consecutive recordings
-----------------------+----------------------------------------------------
Reporter: anonymous | Owner: danielk
Type: defect | Status: closed
Priority: critical | Milestone:
Component: mythtv | Version: head
Severity: high | Resolution: fixed
-----------------------+----------------------------------------------------
Changes (by danielk):
* resolution: => fixed
* status: assigned => closed
Comment:
(In [7427]) Fixes #430.
This fixes two additional problems that cause lost follow on recordings:
* Overrecord race problem, an old problem that was made worse by event
loop improvements.
* Clock drift problem, another old problem.
Fixing the clock drift problem required a MythTV protocol change so you
must upgrade all your backends & frontends. Basically, it adds a
GET_CURRENT_RECORDING query so that we can find out if the slave backend
is recording something the master backend thinks should be done by now.
It is still important to keep the backend clocks in sync with something
line NTP, but with this commit minor clock drift will only mean you might
lose a few seconds of you recording, not the entire follow on recording.
The overrecord race problem is also made worse by a clock drift, basically
if the slave is over 2 seconds "slower" than the frontend you almost
always lost the race, otherwise you lost the race in rough proportion to
how far you were out of sync with the master backend's clock.
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/430>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list