[FFmpeg-trac] #2607(FFmpeg:new): Ffmpeg duplicates and drops frames when given a .ts stream.
FFmpeg
trac at avcodec.org
Tue May 28 11:17:18 CEST 2013
#2607: Ffmpeg duplicates and drops frames when given a .ts stream.
--------------------------------+--------------------------------------
Reporter: Nofew | Type: defect
Status: new | Priority: normal
Component: FFmpeg | Version: git-master
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
--------------------------------+--------------------------------------
Summary of the bug: I have a .ts video from a capture device. When I
attempt to encode it in a less-bloated format, the resulting output has an
incorrect framerate. Upon closer examination it appears that almost every
frame has been dropped and then previous frames duplicated, resulting in
video that not only plays at 15 FPS, but has many duplicate frames that
make it appear to play at 10 FPS.
The source video file is running at 59.94 FPS. Specifying -r (both before
and after -i, or any combination) does not solve the problem.
How to reproduce:
{{{
ffmpeg -i foo.ts -c:v libx264 -an outbar.mp4
ffmpeg version N-53528-g160ea26
built on May 27 2013 15:25:58 with gcc 4.7.3 (GCC)
}}}
Other video codecs and containers produce the same results. It is possible
to take the resulting footage apart with "ffmpeg -i foo.mp4 frame_%d.png"
and see the problematic frames.
Please note that the counter in the bottom right corner of the screen goes
up by 3 every 3 frames (rather than 1 every frame), making it an
unreliable way to test for the bug's presence.
I have uploaded a sample from the .ts file to
upload.mplayerhq.hu/incoming/ under the filename
"Ffmpeg_duplicates_and_drops_frames_when_given_a_ts_stream.ts", along with
a .txt file with the same name that contains a copy of this bug and the
output of "ffmpeg -v 9 -loglevel 99 -i CROP_B.ts -c:v libx264 -an
test.mp4". The log has an identical name to the .ts file, except with .txt
at the end.
The sample is a little strange and may be related to the problem, but even
with its defects ffmpeg is still producing very odd output.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2607>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list