Baptiste Coudurier <[EMAIL PROTECTED]> added the comment: tripp wrote: > New submission from tripp <[EMAIL PROTECTED]>: > > hi, > > ffmpeg misreports duration of elementary mpeg2. > i'd expect this to be 1005 failure on any ntsc > material with soft pulldown. > but i've also seen it on most pal streams too. > > ffmpeg -i b.m2v > FFmpeg version SVN-r14231, Copyright (c) 2000-2008 Fabrice Bellard, et al. > configuration: --enable-memalign-hack --enable-postproc --enable-swscale > --ena > ble-gpl --enable-liba52 --enable-libfaac --enable-libfaad --enable-libgsm > --enab > le-libmp3lame --enable-libnut --enable-libvorbis --enable-libtheora > --enable-lib > xvid --enable-libx264 --disable-ffserver --disable-ffplay --enable-avisynth > --en > able-small --enable-pthreads --extra-ldflags=-static > --extra-cflags=-mtune=penti > um4 -mfpmath=sse -msse -fno-strict-aliasing > libavutil version: 49.7.0 > libavcodec version: 51.60.0 > libavformat version: 52.17.0 > libavdevice version: 52.0.0 > built on Jul 15 2008 04:17:40, gcc: 4.3.1 > Input #0, mpegvideo, from 'b.m2v': > Duration: 00:00:20.63, bitrate: 9199 kb/s > Stream #0.0: Video: mpeg2video, yuv420p, 720x576 [PAR 64:45 DAR 16:9], > 9200 > kb/s, 25.00 tb(r) > Must supply at least one output file > > actual duration 1min.23sec > bitrate is aslo woefully off. 2500k
That is the problem, to compute the exact duration, file would need to be fully parsed to compute frame number, and then duration. Here to be fast it takes filesize and bitrate to compute duration, since you file is clearly not cbr, the computation is wrong. [...] ______________________________________________________ FFmpeg issue tracker <[EMAIL PROTECTED]> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue544> ______________________________________________________
