[FFmpeg-trac] #2435(FFmpeg:new): moov atom not found

FFmpeg trac at avcodec.org
Fri Apr 5 22:53:12 CEST 2013

#2435: moov atom not found
               Reporter:  KSHawkEye  |                  Owner:
                   Type:  defect     |                 Status:  new
               Priority:  important  |              Component:  FFmpeg
                Version:  git-       |               Keywords:  moov atom
  master                             |  not found
             Blocked By:             |               Blocking:
Reproduced by developer:  0          |  Analyzed by developer:  0
 I'm getting "moov atom not found" with the latest version of the FFmpeg

 Here is the result of the following command:
 ffmpeg -v 9 -loglevel 99 -i "20121006182827-0006KM.mov"

 ffmpeg version N-51511-g599866f Copyright (c) 2000-2013 the FFmpeg
   built on Apr  1 2013 12:44:46 with gcc 4.8.0 (GCC)
   configuration: --enable-gpl --enable-version3 --disable-w32threads
 --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r
 --enable-gnutls --enable-libass --enable-libbluray --enable-libcaca
 --enable-libfreetype --enable-libgsm --enable-libilbc --enable-libmp3lame
 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg
 --enable-libopus --enable-librtmp --enable-libschroedinger --enable-
 libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-
 libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx
 --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
   libavutil      52. 24.100 / 52. 24.100
   libavcodec     55.  2.100 / 55.  2.100
   libavformat    55.  1.100 / 55.  1.100
   libavdevice    55.  0.100 / 55.  0.100
   libavfilter     3. 48.105 /  3. 48.105
   libswscale      2.  2.100 /  2.  2.100
   libswresample   0. 17.102 /  0. 17.102
   libpostproc    52.  2.100 / 52.  2.100
 Splitting the commandline.
 Reading option '-v' ... matched as option 'v' (set logging level) with
 argument '9'.
 Reading option '-loglevel' ... matched as option 'loglevel' (set logging
 level) with argument '99'.
 Reading option '-i' ... matched as input file with argument
 Finished splitting the commandline.
 Parsing a group of options: global .
 Applying option v (set logging level) with argument 9.
 Successfully parsed a group of options.
 Parsing a group of options: input file
 Successfully parsed a group of options.
 Opening an input file: C:\Users\Kyle\Desktop\20121006182827-0006KM.mov.
 [mov,mp4,m4a,3gp,3g2,mj2 @ 0210e7c0] Format mov,mp4,m4a,3gp,3g2,mj2 probed
 with size=2048 and score=100
 [mov,mp4,m4a,3gp,3g2,mj2 @ 0210e7c0] ISO: File Type Major Brand: qt
 [mov,mp4,m4a,3gp,3g2,mj2 @ 0210e7c0] moov atom not found
 [AVIOContext @ 0210ece0] Statistics: 32768 bytes read, 1 seeks
 C:\Users\Kyle\Desktop\20121006182827-0006KM.mov: Invalid data found when
 processing input

 I don't know if this is a Windows only bug, but it occurs with a version
 compiled with MinGW-w64 and MSVC.

 This issue seems to be only 32-bit related, the 64-bit versions work. It
 also might be related to a issue with large files.

 The build used to get the error is:

 The issue happens with the following file:

 This file is very large (4.7G) and has the MD5 hash:

 I am willing to provide any further information needed.

 This issue happens with ffmpeg, ffplay, and ffprobe.

Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2435>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list