[mythtv-users] mythburn error trying to process cut-list -- translation?

[Carl Fongheiser]

On 5/28/07, Craig Huff <huffcs at yahoo.com> wrote:
>
> I am working on getting mythArchive to work for me to produce archive DVDs
> with closed captioning intact and audio keeping in sync with the video.
>
> If I don't use project X to cut the commercials out and try to use the
> native mythArchive processing for this, I get the following messages in the
> mythburn.log file:
>
> Video resolution is 720 by 480
> *************************************************************
> Processing file 1073_20070517211400.mpg of type recording
> *************************************************************
> File type is 'mpeg'
> Video codec is 'mpeg2video'
> File has a cut list - running mythtranscode to remove unwanted segments
> 2007-05-27 17:08:13.385 Using runtime prefix = /usr
> 2007-05-27 17:08:13.490 New DB connection, total: 1
> 2007-05-27 17:08:13.529 Enabled verbose msgs: important
> 2007-05-27 17:08:13.531 New DB connection, total: 2
> 2007-05-27 17:08:13.756 Parser not found for Codec Id: 94210 !
> Mux rate: 6.49 Mbit/s
> Failed while running mythtranscode to cut commercials and/or clean up an
> mpeg2 file.
> Result: 60160, Command was mythtranscode --mpeg2 --honorcutlist -c 1073 -s
> 2007-05-17T21:14:00 -o /video/temp/work/1/tmp
> Failed to run mythtranscode to remove unwanted segments
>
>
> I haven't been able to deduce what mythtranscode return value 60160
> means.  Can anyone help me figure out what is going on (or I suppose it
> would be more accurate to say what *isn't* going on)? ;-)


Sure. It's kicking out the result of the os.system() call, which returns the
status as formatted by the Unix wait() call.  The actual exit status is in
the high byte. (The low byte would indicate the signal that caused the
process to die, if that happened.)  In this case, the exit status is 235,
which is TRANSCODE_BUGGY_EXIT_WRITE_FRAME_ERROR.  I can't really tell you
where to go from there;  mythtranscode exits with that status in a few
different circumstances.

In case you can't figure it out from this, the time format isn't your
problem.

Carl Fongheiser
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20070528/d628930c/attachment.htm