<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>I have had a few instances now, where transcode jobs get stuck and would
run presumably forever. Oddly, the last 3 times have all been with the
same program (different episodes, obviously) and the progress seems to get stuck
in almost the exact same spot, around 35%-38%.</DIV>
<DIV> </DIV>
<DIV>Aside from the decidedly negative effect of this causing everything else in
the queue to take a permanent hiatus until this job is stopped, it also has the
nasty effect of filling up the backend log with line after line of this...</DIV>
<DIV> </DIV>
<DIV>2010-11-30 18:29:55.710 Couldn't open file abort.dat</DIV>
<DIV>2010-11-30 18:29:55.718 Failed to decode frame. Position was: 0</DIV>
<DIV> </DIV>
<DIV>I have had two occasions where the jobs were set up just before going to
bed for the night, and the jobs ran for 10 hours before I discovered them, and
the backend log was in the 100’s of MBs.</DIV>
<DIV> </DIV>
<DIV>The only way I have been able to stop these jobs is to go into a terminal,
find the PID for mythtranscode and kill it. Then find the .tmp file for
the job and manually delete it. Any attempts to pause it, stop it, etc
from the Info Center are met with failure.</DIV>
<DIV> </DIV>
<DIV>I only run lossless transcodes to remove commercial cuts.</DIV>
<DIV> </DIV>
<DIV>Has anyone else encountered this issue? More importantly, is there a
better way to kill these jobs?</DIV>
<DIV> </DIV>
<DIV>Thanks</DIV></DIV></DIV></BODY></HTML>