Sorry for the false alarm. It seems to be a bug in the python wrapper.
ffmpeg generates all frames if I extract frames into an image sequence.
On 04/30/2013 04:52 PM, Tom Evans wrote:
> On Tue, Apr 30, 2013 at 3:46 PM, Peter Rennert <p.rennert at cs.ucl.ac.uk> wrote:
>> Hi,
>>>> I am trying to convert an image sequence to an image to a video. I do not
>> care about the framerate at all, I just need to make absolutely sure that
>> consecutive frames in the resulting video are exactly the consecutive images
>> of the sequence. I do neither want to have images of the sequence dropped
>> nor duplicated.
>>>> I have an image sequence:
>>>> 2013-02-19.00-00-00.v0.00000.png
>> - - -
>> 2013-02-19.00-00-00.v0.01760.png
>>>> I tried several things, of of them:
>>>> $ ffmpeg -f image2 -r 29.97 -i 2013-02-19.00-00-00.v0.%05d.png -c:v libx264
>> test.mp4
>>>> (see output below)
>>>> I also tried -r 30 after the image2 and after libx264 and both. However, I
>> seem (stepping through the video using the ffmpeg python wrapper ffvideo) to
>> get a video of only 1753 frames or some other values around. How can I fix
>> that?
>>>>>> Thanks,
>>>> Peter
>>>> ffmpeg output:
>>>> ffmpeg version 1.0.5 Copyright (c) 2000-2012 the FFmpeg developers
>> built on Mar 10 2013 12:20:58 with gcc 4.7.2 (GCC) 20121109 (Red Hat
>> 4.7.2-8)
> This is probably too old, try building from git head and see if that
> has the same issues.
>> Cheers
>> Tom
> _______________________________________________
> ffmpeg-user mailing list
>ffmpeg-user at ffmpeg.org>http://ffmpeg.org/mailman/listinfo/ffmpeg-user