New submission from compumike <[email protected]>:

The latest SVN build (r19545) of ffmpeg reports "Duration: 00:27:39.02, start:
0.000000" on a file:
  http://www.nerdkits.com/files/capture020.m2t (18MB) 
when the file only contains 5 seconds of video!  Video is an HDV capture
directly from dvgrab and plays correctly in xine and mplayer and ffplay.  This
issue happens with all of my HDV capture files.  Even though the files seem to
play OK, this start/duration problem seems to be propagating downstream into
tools like kdenlive, seriously breaking their ability to use these files in
editing work.

User |DrV| on #ffmpeg tried this with ffmpeg 0.5 and reports: "with ffmpeg 0.5
release, i get Duration: 00:00:05.53, start: 1653.487767, bitrate: 26439 kb/s,
so it looks like a regression since then...".  These start and duration numbers
are what I'd actually expect (and what downstream libavformat-dependent tools
would expect).

Please let me know if more information is needed or where I can look in the
codebase to help hunt for the regression.  Thanks!

Here is the full "ffmpeg -i" output from the latest SVN build:

=====

FFmpeg version SVN-r19545, Copyright (c) 2000-2009 Fabrice Bellard, et al.    
  configuration: --prefix=/usr --extra-cflags='-Wall -g '
--libdir='${prefix}/lib' --shlibdir='${prefix}/lib' --bindir='${prefix}/bin'
--incdir='${prefix}/include/ffmpeg' --enable-shared --enable-libmp3lame
--enable-gpl --enable-libfaad --mandir='${prefix}/share/man' --enable-libvorbis
--enable-pthreads --enable-libfaac --enable-libxvid --enable-postproc
--enable-x11grab --enable-libgsm --enable-libopencore-amrnb
--enable-libopencore-amrwb --enable-libx264 --enable-libtheora
--enable-libdc1394 --enable-libspeex --enable-nonfree --disable-stripping
--enable-avfilter --enable-libdirac --disable-decoder=libdirac
--enable-libschroedinger --disable-encoder=libschroedinger
--enable-avfilter-lavf --enable-libopenjpeg --enable-version3 --disable-altivec
--disable-armv5te --disable-armv6 --disable-vis
  libavutil     50. 3. 0 / 50. 3. 0
  libavcodec    52.32. 0 / 52.32. 0
  libavformat   52.36. 0 / 52.36. 0
  libavdevice   52. 2. 0 / 52. 2. 0
  libavfilter    0. 5. 0 /  0. 5. 0
  libswscale     0. 7. 1 /  0. 7. 1
  libpostproc   51. 2. 0 / 51. 2. 0
  built on Jul 30 2009 11:05:36, gcc: 4.3.3

Seems stream 0 codec frame rate differs from container frame rate: 59.94
(60000/1001) -> 29.97 (30000/1001)
Input #0, mpegts, from 'capture020.m2t':
  Duration: 00:27:39.02, start: 0.000000, bitrate: 88 kb/s
  Program 100
    Stream #0.0[0x810]: Video: mpeg2video, yuv420p, 1440x1080 [PAR 4:3 DAR
16:9], 25000 kb/s, 29.97 tbr, 90k tbn, 59.94 tbc
    Stream #0.1[0x814]: Audio: mp2, 48000 Hz, 2 channels, s16, 384 kb/s
    Stream #0.2[0x815]: Data: 0x00a0
    Stream #0.3[0x811]: Data: 0x00a1
At least one output file must be specified
Seems stream 0 codec frame rate differs from container frame rate: 59.94
(60000/1001) -> 29.97 (30000/1001)
Input #0, mpegts, from 'capture020.m2t':
  Duration: 00:27:39.02, start: 0.000000, bitrate: 88 kb/s
  Program 100
    Stream #0.0[0x810]: Video: mpeg2video, yuv420p, 1440x1080 [PAR 4:3 DAR
16:9], 25000 kb/s, 29.97 tbr, 90k tbn, 59.94 tbc
    Stream #0.1[0x814]: Audio: mp2, 48000 Hz, 2 channels, s16, 384 kb/s
    Stream #0.2[0x815]: Data: 0x00a0
    Stream #0.3[0x811]: Data: 0x00a1
At least one output file must be specified

----------
messages: 6601
priority: normal
status: new
substatus: new
title: MPEGTS misreports start/duration, breaking downstream editing tools
type: bug

_____________________________________________________
FFmpeg issue tracker <[email protected]>
<https://roundup.ffmpeg.org/roundup/ffmpeg/issue1297>
_____________________________________________________

Reply via email to