<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
<br><br>> Date: Mon, 13 Dec 2010 10:12:37 +0000<br>> From: knowledgejunkie@gmail.com<br>> To: mythtv-users@mythtv.org<br>> Subject: Re: [mythtv-users] Recording unavailable , zero length at incorrect time<br>> <br>> On 13 December 2010 09:48, Sean Salisbury <sean_salisbury@hotmail.com> wrote:<br>> > I recently updated my myth backend and frontends to 0.24 via mythbuntu repos<br>> > and have started experiencing unavailable recordings. Having looked through<br>> > the mailing lists and tried various suggested methods (use quick tuning,<br>> > delete cards in setup and start again) no solution has been found.<br>> ><br>> > To try and track down any errors I enabled backend logging to try and find<br>> > an obvious problem however I am now confused.<br>> ><br>> > Last night I had "Mad Max" scheduled to record at 22:00 and the backend logs<br>> > shows this nicely<br>> ><br>> ><br>> > 2010-12-12 21:57:30.342 Scheduler: Update next_record for 115<br>> > --- print list start ---<br>> > Title - Subtitle Ch Station Day Start End S C I T N<br>> > Pri<br>> > Mad Max 24 ITV4 12 22:00-23:55 1 3 1 S 3 1<br>> > From Hell 31 FIVE US 13 22:00-00:35 1 3 1 S 3 1<br>> > Severance 1 BBC ONE 17 23:30-01:00 1 3 1 S 3 1<br>> > --- print list end ---<br>> > 2010-12-12 21:57:30.345 Scheduled 3 items in 0.1 = 0.00 match + 0.06 place<br>> ><br>> ><br>> > However the next mention of recording of Mad Max comes nearly 6 hours late<br>> > with the following from the backend log<br>> ><br>> ><br>> > 2010-12-13 03:47:08.356 TVRec(4): ASK_RECORDING 4 29 0 0<br>> > 2010-12-13 03:47:08.357 MythEvent: ASK_RECORDING 4 29 0 0<br>> > 2010-12-13 03:47:08.358 MythSocket(88e4240:41): write -> 41 589<br>> > BACKEND_MESSAGE[]:[]ASK_RECORDING 4 29 0 0[]:[]Mad Max[]:[][]:[]N...<br>> > 2010-12-13 03:47:08.485 MythEvent: SYSTEM_EVENT REC_PENDING SECS -20829<br>> > CARDID 3 CHANID 1024 STARTTIME 2010-12-12T22:00:00 SENDER elliot<br>> <br>> For some reason, your Mad Max rule was set to start early by -20829<br>> seconds (note the negative sign) - this has the effect of starting the<br>> recording a little over 5:45 hours _late_ due to the negative timing,<br>> which agrees with the actual recording.<br>> <br>> Make sure you have not got a ridiculous system-wide global pre-roll<br>> setting or per-rule start early setting in effect. If these are both<br>> set to zero, I'd run the optimize_db.pl script to check the integrity<br>> of the MythTV database.<br>> <br>> Cheers,<br>> Nick<br>> <br>> -- <br>> Nick Morrott<br>> <br>> MythTV Official wiki: http://mythtv.org/wiki/<br>> MythTV users list archive: http://www.gossamer-threads.com/lists/mythtv/users<br>> <br>> "An investment in knowledge always pays the best interest." - Benjamin Franklin<br>> _______________________________________________<br>> mythtv-users mailing list<br>> mythtv-users@mythtv.org<br>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users<br><br><br>Thanks Nick<br><br>The only setting tweaked from default and is still different from default is global early start recording setting of 90 seconds.<br><br>I have just run optimize script and hopefully this will fix it, fingers crossed.<br><br>Sean<br> </body>
</html>