>I don't know how to resolve this problem. Could the large
>buffer (-u 1024,2) be responsible for this? Maybe transcode
>will omit the terminal frames of the data in the buffer.
That's certainly possible; transcode interprets ^C as "stop NOW", not
"stop when you're finished with what's in the buffers". If you know the
length of the clip ahead of time, you could use -c to ensure you get the
right amount; otherwise, wait an extra 20-30 seconds (actually 1024/fps
since you use 1024 buffers, so ~35 seconds for NTSC or ~41 seconds for
PAL) after the video finishes before pressing ^C, and use -c on the
encoding sessions to specify the exact frame range you want to keep.
On the other hand, I have to admit I'd be surprised if you actually
made use of even 10-20 seconds of buffers without ending up with dropped
frames somewhere. What does the buffer status line (the part at the end
of the progress line that reads "( 1| 2| 3) or the like) look like while
you're capturing, i.e. how high do any of the numbers go?
--Andrew Church
[EMAIL PROTECTED]
http://achurch.org/
