<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
System clock is fine on all machines and all running ntp correctly, first two things I checked after pre/post time offset in UI.<BR>
<BR>
Also gone back to single machine setup alongside a clean install of 0.24 as an attempt to eliminate/narrow down problem space.<BR>
<BR>
<BR>
Sean<BR><BR>
<BR>
> Date: Fri, 17 Dec 2010 11:24:38 +0000<BR>> From: mikep@randomtraveller.org.uk<BR>> To: mythtv-users@mythtv.org<BR>> Subject: Re: [mythtv-users] Recording unavailable , zero length at incorrect time<BR>> <BR>> On 16/12/10 21:22, Sean Salisbury wrote:<BR>> ><BR>> > These showed the pending recordings having the expected zero offsets right<BR>> > upto roughly the start time, however recordings continued starting late<BR>> > suggesting corruption somewhere else when starting recording.<BR>> ><BR>> I know this is going to sound like a very simple, basic suggestion, but: have <BR>> you checked that your host clock is accurate? This would give the syptoms you <BR>> describe.<BR>> <BR>> You should be running ntp on your box. If more than one box, it is almost <BR>> essential to run ntp on them all to ensure synchronisation.<BR>> <BR>> -- <BR>> <BR>> Mike Perkins<BR>> <BR>> _______________________________________________<BR>> mythtv-users mailing list<BR>> mythtv-users@mythtv.org<BR>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users<BR> </body>
</html>