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).
It only happens when the list of timecodes to rip go beyond the duration
of the video, but in a script that will typically be the case.
An alternative to using lots of timecodes is of course to use a frame
interval:
--frame_interval 30000/1001
However, transcode (1.1.0-CVS or 1.0.x) doesn't support fractional
frame-intervals, and using integers or even decimals is not accurate
enough. We've discussed this before, and it would be great if support
could be added. In the meantime, let's try to figure out this OSX quirk.
I posted a good trace on mantis.
Dave
Francesco Romani wrote:
Hi there,
1.1.0 is in sight. Eventually.
With new sequential decoder committed, my feature FIFO is now empty.
Before to branch CVS and to go alpha, however, there are a few pending
issues that I'd like to summarize here. Our mantis bugtracker still is
the official issue list, so I'll update it ASAP.
Without a specific priority order:
1. new import_x11 code is largely untested.
2. same as above for ALSA code. There is still room for some basic
optimizations
3. tctimer (needed by import_x11) is likely to be broken
4. ImageMagick 6.3.x with HDR broke our modules
5. new sequential decoder (disabled by default) needs careful testing
6. SDL problems (misdetection) on MacOsX recentely reported
7. Of course, issues already on mantis deserves *at very least*
investigation.
If I miss something, *please* (in *strict* priority order) report it
on http://tcfoundry.hostme.it/mantis _and_ reply to this mail.
A few more words about issue #4 above.
I'd like rewrite our IM modules using higher-level MagickWand interface,
(http://www.imagemagick.org/script/magick-wand.php) , with hope that
this cause to us less troubles than past.
There just a potential problem, backporting those fixes to 1.0.x trunk
will lead to a very spicy (= a fair pile of new code and dropping gtk+
support is pretty much for a bugfix-only branch!) 1.0.4 release :)
Well, I guess that this will help in promoting 1.1.0 branch :P
Thoughts?
Bests,
