[FFmpeg-trac] #377(undetermined:new): ffmpeg reports inaccurate length of some gxf files

[FFmpeg]

#377: ffmpeg reports inaccurate length of some gxf files
----------------------------------+---------------------------
Reporter:  acloutier              |       Owner:
    Type:  defect                 |      Status:  new
Priority:  important              |   Component:  undetermined
 Version:  git                    |  Resolution:
Keywords:  gxf ffmpeg length bug  |  Blocked By:
Blocking:                         |  Reproduced:  0
Analyzed:  0                      |
----------------------------------+---------------------------

Comment (by acloutier):

 Hmm.. it's possible that our in-house tool used to 'trim' these files
 smaller ( by replacing un-needed video with black ) didn't set the field
 correctly.

 If it helps, here's the output for a file that doesn't have the issue ( it
 wasn't 'trimmed', so it's straight from our video encoder ):
 {{{

 ffmpeg -i /archive/rawVideo/2009/05/06/20090506215701002.gxf
 ffmpeg version 0.7-rc1, Copyright (c) 2000-2011 the FFmpeg developers
   built on May 24 2011 15:20:15 with gcc 4.5.3
   configuration: --prefix=/opt/ffmpeg/0.7-rc1 --extra-cflags='-O3 -fPIC
 -ffast-math' --extra-ldflags='-O3 -fPIC -ffast-math' --extra-
 libs='-L/usr/local/lib -R/usr/local/lib' --disable-asm --disable-ssse3
 --disable-amd3dnow --disable-amd3dnowext --enable-hardcoded-tables
 --enable-gpl --enable-nonfree --disable-ffserver --disable-ffplay
 --disable-debug --disable-protocol=udp --disable-encoder=nellymoser
 --disable-network --enable-swscale --enable-libmp3lame --enable-pthreads
 --enable-libfaac --enable-libx264
   libavutil    50. 40. 1 / 50. 40. 1
   libavcodec   52.120. 0 / 52.120. 0
   libavformat  52.108. 0 / 52.108. 0
   libavdevice  52.  4. 0 / 52.  4. 0
   libavfilter   1. 77. 0 /  1. 77. 0
   libswscale    0. 13. 0 /  0. 13. 0
 Input #0, gxf, from '/archive/rawVideo/2009/05/06/20090506215701002.gxf':
   Duration: 02:03:59.13, start: 0.000000, bitrate: 11551 kb/s
     Stream #0.0: Video: mpeg2video (4:2:2), yuv422p, 720x512 [PAR 128:135
 DAR 4:3], 10000 kb/s, 59.94 fps, 29.97 tbr, 59.94 tbn, 59.94 tbc
     Stream #0.1: Audio: pcm_s16le, 48000 Hz, 1 channels, s16, 768 kb/s
     Stream #0.2: Audio: pcm_s16le, 48000 Hz, 1 channels, s16, 768 kb/s
     Stream #0.3: Data: [0][0][0][0] / 0x0000
 At least one output file must be specified

 }}}


 Is there some flag we can pass ffmpeg to bypass this bad fps guess? I see
 some reference to putting -r ''before'' the -i to set the input frame
 rate, but that doesn't work.

-- 
Ticket URL: <https://avcodec.org/trac/ffmpeg/ticket/377#comment:5>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker