On Tue, 17 Jul 2007, David Liontooth wrote: > > Salve Francesco, > > I just submitted a bug report on mantis on a hang in OSX (MacIntel) > during frame ripping. > > To get frame-accurate thumbnails every ten seconds from a video, I use a > long list of time codes: > > transcode -q 0 -o $FIL.img -y im -F png -x ffmpeg,null -i $FIL.avi -c \ > 0:00:00-0:00:00.1,0:00:10-0:00:10.1,0:00:20-0:00:20.1,0:00:30-0:00:30.1,0:00:40-0:00:40.1,0:00:50-0:00:50.1,\ > 0:01:00-0:01:00.1,0:01:10-0:01:10.1,0:01:20-0:01:20.1,0:01:30-0:01:30.1,0:01:40-0:01:40.1,0:01:50-0:01:50.1,\ > and so on for videos up to 75 minutes long. > > transcode CVS rips the frames correctly, but if there are time codes > left over beyond the duration of the video file, it hangs on OSX (both > the 1.1.0-cvs and the 1.0.x work fine on Linux).
A simpler case: for a ten-minute video, this will hang: transcode -q 0 -o *.img/png/test -y im -F png -x ffmpeg,null -i *.avi -c 0:10:05-0:10:05.1,0:10:09-0:10:09.1 If there's two or more timecodes beyond the end of the file, it hangs reliably. A single excessive timecode is tolerated. The kdump I submitted may not be that useful, as it's mainly bash information; I can do a trace of the transcode process if needed. Dave
