This is happening at the very end though, after the video has been
processed. In some instances I have been able to continue and ignore
this error, although only rarely. The source of this video is a Sony
Handycom. On my system (Mandrake 2005) I have no errors and can process
the video for NTSC fine. However others have emailed me with problems,
mostly with PAL video. Does the gdb session that I posted previously
shed any light on the matter?
A little more detail: I capture the video using dvgrab. I have used
multiple capture formats and it doesn't appear to make any difference
when transcoding the video. I use transcode in my software
(sourceforge.net/projects/dvd-homevideo) and I have received several
emails from users about this broken pipe issue - I really need to find a
solution.
Jacob Meuser wrote:
On Fri, May 19, 2006 at 08:38:59PM -0500, Shane wrote:
I tried the -x ffbin instead of -x dv and still am having the same
issue. The issue is still a broken pipe, and the output was:
sh: line 1: 17352 Broken pipe ffmpeg -i "dv/dv_file-001.dv" -f
yuv4mpegpipe -y /tmp/ffbin2transcode-audio.hvvYtM >/dev/null 2>&1
sh: line 1: 17350 Broken pipe ffmpeg -i "dv/dv_file-001.dv" -f s16le -y
/tmp/ffbin2transcode-audio.R6QkYt >/dev/null 2>&1
This seems to be more prevalent with PAL rather than NTSC. This
continues to be a major issue, can anyone shed some light on this?
to quote your error report:
(decode_dv.c) header parsing failed (2)
(decode_dv.c) audio: 32000 Hz, 2 channels
(decode_dv.c) header parsing failed (2)
(decode_dv.c) NTSC video: 720x480 framesize=120000 sampling=1
seems you have bad DV source files. I assume this is probably why
'-x ffbin' does not work either.
why this is happening, I don't know. where do these DV files come
from?
