New submission from Henk Schoneveld <belca...@zonnet.nl>: ffmpeg -i ../trial/test.split.98.ts -an -vcodec copy -f rawvideo howmanyframes.h264 FFmpeg version SVN-r23993, Copyright (c) 2000-2010 the FFmpeg developers built on Jul 21 2010 12:02:11 with gcc 4.2.2 20070909 (prerelease) (4.2.2-0.RC.1mdv2008.0) configuration: --prefix=/usr --enable-gpl --enable-libfaac --enable-libmp3lame --enable-pthreads --disable-ffserver --enable-ffplay --as=yasm --enable-nonfree --enable-libx264 --enable-libxvid libavutil 50.19. 1 / 50.19. 1 libavcodec 52.78. 1 / 52.78. 1 libavformat 52.72. 0 / 52.72. 0 libavdevice 52. 2. 0 / 52. 2. 0 libavfilter 1.20. 1 / 1.20. 1 libswscale 0.11. 0 / 0.11. 0 [mpegts @ 0x8d17510] max_analyze_duration reached Input #0, mpegts, from '../trial/test.split.98.ts': Duration: 00:00:11.88, start: 1764.000000, bitrate: 3837 kb/s Program 1 Stream #0.0[0x1011]: Video: mpeg2video, yuv420p, 704x576 [PAR 16:11 DAR 16:9], 10000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc File 'howmanyframes.h264' already exists. Overwrite ? [y/N] y Output #0, rawvideo, to 'howmanyframes.h264': Metadata: encoder : Lavf52.72.0 Stream #0.0: Video: mpeg2video, yuv420p, 704x576 [PAR 16:11 DAR 16:9], q=2-31, 10000 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0.0 -> #0.0 Press [q] to stop encoding frame= 300 fps= 0 q=-1.0 Lsize= 5379kB time=11.88 bitrate=3708.9kbits/s video:5379kB audio:0kB global headers:0kB muxing overhead 0.000000%
As can be observed PAL 25fps, frame duration 0.04 Duration: 00:00:11.88 which translates to 297frames. frame= 300 With a copy nothing gets lost, but in any encoding always 2-frames get lost, mplayer and all other depending applications suffer from this. This is related to issue 2020 Mplayer is even more wrong, according to ID_LENGTH=4.56 but when played, it plays V:1775.8 298/298 2 frames missing. ---------- messages: 11544 nosy: belcampo priority: normal status: new substatus: new title: Counting matters, not all parts of ffmpeg agree, 2-frames get lost type: bug ________________________________________________ FFmpeg issue tracker <iss...@roundup.ffmpeg.org> <https://roundup.ffmpeg.org/issue2144> ________________________________________________