[FFmpeg-user] FFmpeg accuracy issues.

Shlomi Shalem shlomi at shalem.co
Fri Jul 27 16:27:18 CEST 2012


Thanks for your answer, Carl!

I have been reading a little bit about the 'analyzedurayion' flag. I tried
to use it as follows:

'*ffmpeg -t 00:00:10.000 -analyzeduration 0 -i foo.wav trimmed_foo.wav -ss
00:00:25.000*'.

The full console output is:

* foo.wav trimmed_foo.wav -ss 00:00:25.000*
*ffmpeg version 0.11.1 Copyright (c) 2000-2012 the FFmpeg developers*
*  built on Jul 25 2012 19:55:05 with gcc 4.2.1 (Apple Inc. build 5664)*
*  configuration: --enable-gpl --enable-shared --enable-pthreads
--enable-libx264 --enable-libmp3lame*
*  libavutil      51. 54.100 / 51. 54.100*
*  libavcodec     54. 23.100 / 54. 23.100*
*  libavformat    54.  6.100 / 54.  6.100*
*  libavdevice    54.  0.100 / 54.  0.100*
*  libavfilter     2. 77.100 /  2. 77.100*
*  libswscale      2.  1.100 /  2.  1.100*
*  libswresample   0. 15.100 /  0. 15.100*
*  libpostproc    52.  0.100 / 52.  0.100*
*[wav @ 0x10180e800] max_analyze_duration 0 reached at 0*
*Guessed Channel Layout for  Input Stream #0.0 : mono*
*Input #0, wav, from 'foo.wav':*
*  Duration: 00:00:40.42, bitrate: 705 kb/s*
*    Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, mono,
s16, 705 kb/s*
*Output #0, wav, to 'trimmed_foo.wav':*
*  Metadata:*
*    encoder         : Lavf54.6.100*
*    Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, mono,
s16, 705 kb/s*
*Stream mapping:*
*  Stream #0:0 -> #0:0 (pcm_s16le -> pcm_s16le)*
*Press [q] to stop, [?] for help*
*size=     864kB time=00:00:10.03 bitrate= 705.6kbits/s    *
*video:0kB audio:864kB global headers:0kB muxing overhead 0.005199%*

As you can see, it didn't solve the problem. Am I misusing it? Any other
idea?

Thanks a lot for your help!

On Fri, Jul 27, 2012 at 4:46 PM, Carl Eugen Hoyos <cehoyos at ag.or.at> wrote:

> Shlomi Shalem <shlomi <at> shalem.co> writes:
>
> > *[wav @ 0x10180e800] max_analyze_duration 5000000 reached at 5015510*
>
> This is the relevant line answering your question regarding wav.
> There is an option -analyzeduration
>
> Regarding mov, I am not completely sure, I suspect the input
> duration is stored in the file.
>
> If this does not answer your question, please post complete, uncut
> console output (not just a part of it).
>
> Carl Eugen
>
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>


More information about the ffmpeg-user mailing list