<html><div style='background-color:'><P>This is my first post - If I have sent this email incorrectly please let me know. I intended it to join a current thread.</P>
<P>I just got my mythtv up and running over this past weekend. :-) I'm running RH9 on at 1.1Ghz Athlon, WinTV PVR 250.</P>
<P>It was running fine over the weekend and I finally moved it to the living room Sunday night - (no wireless access point yet). The backend began to crash on me regularly so I had to move it back to the office. This cutlist update problem appears to be what is hanging up my backend.</P>
<P>Yesterday my mythtv was rebooted around 4:00 and stayed up and buzy through primetime. At around 11:00 I see the following entries in the mythbackend.log:</P><FONT size=2>
<P>2004-03-02 23:01:52 Transcoding from /mythtv/recordings/1002_20040228233000_20040229000000.nuv to /mythtv/recordings/1002_20040228233000_20040229000000.nuv.tmp</P>
<P>2004-03-02 23:01:52 Transcoding /mythtv/recordings/1002_20040228233000_20040229000000.nuv aborted because of cutlist update</P></FONT>
<P>These continue every minute until this morning around 9:00 when I rebooted the machine.</P>
<P>It doesn't cause the mythbackend to completly die but my 1:30 am recording of Futurama only recorded 7 minutes of data. But there is no problem indicated in the log. The backend appears happy until I try to watch livetv, delete an existing program, or such - then I finally get the "the backend does not appear to be up" message and know I need to reboot.</P>
<P>After reading this thread I realized the problem. I had started the transcode on the 2/28 file several days ago as a test and I guess I must have rebooted my machine during the original automated commercial scan. I knew my transcode didn't work but I didn't know it was going to keep trying forever.</P>
<P>I have now just deleted that recording and the transcode is no longer being attempted. </P>
<P>I wanted to bring this to light just to see if this problem is know to degenerate the backend. If so, is there some way to recognize the error and do the <FONT size=2>mythcommflag --force automatically? Or maybe just cancel the transcode on that file?</FONT></P>
<P><FONT size=2>Now that my problem is known, (I hope this was my problem) I'm happy - I can move mythtv back to living room.</FONT></P>
<P><BR><BR><BR> </P>
<DIV>
<DIV>
<DIV align=center><FONT face="Lucida Handwriting, Cursive" color=#3300ff>Stephens Johnnson </FONT></DIV>
<DIV align=center><FONT color=#339933>email: <A href="mailto:StephensJohnson@hotmail.com">StephensJohnson@hotmail.com</A> </FONT></DIV>
<DIV align=center> </DIV></DIV></DIV></div><br clear=all><hr> <a href="http://g.msn.com/8HMBENUS/2743??PS=">Create a Job Alert on MSN Careers and enter for a chance to win $1000!</a> </html>