I stumbled over some similar issue when using the "-r 1" option. See
ticket http://trac.ffmpeg.org/ticket/3990 for details and some possible
work-around using the "fps" filter.
Regards,
Tobias
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http:
Hi Gergely,
On Mon, Jul 27, 2015 at 15:46:48 +, Lukácsy Gergely wrote:
> I think ffmpeg never outputs the header information regarding duration and
> such.
I think it does. It doesn't by default output the individual streams'
duration, though.
$ ffmpeg -i out_ffmpeg.mp4
Input #0, mov,mp4,
> Smaller, you meant to say? Actually, you mistyped 496?
Damn... yes, I mistyped it, the correct duration is 296 (as you noticed in the
console log).
> Perhaps that's according to the header, and the actual video stream is
> longer,
resulting in about 300 seconds.
I think ffmpeg never outputs
On Fri, Jul 24, 2015 at 09:15:16 +, Gergely Lukácsy wrote:
Apart from everything else:
> The strange thing that the total number of frames (300) produced is bigger
> than what the video duration (496 s) and the 1 sec framerate would indicate.
Smaller, you meant to say? Actually, you mistype
Greetings, FFmpeg users!
I'm trying to OCR some presentation videos, using ffmpeg to extract frames. I
need to figure out the exact locations of each transitions, and there's no
other method to do that than inspecting the number of the output frame.
The command is the following:
/home/gergo/ff
