View Bug Details

IDProjectCategoryView StatusLast Update
0001683DCP-o-maticBugspublic2024-01-18 00:10
Reporteroverlookmotel Assigned Tocarl  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
PlatformMacOSOS XOS Version10.14
Product Version2.14.8 
Summary0001683: Error opening file
Description

DCP-o-matic is erroring when trying to open a particular MP4 file.

In the GUI, it says: Error: Could not open /path/to/file.mp4. Logfile includes:

Sat  7 Dec 21:24:53 2019: FFmpeg: error reading header
Sat  7 Dec 21:24:53 2019: ERROR: Error in job: Could not open /path/to/file.mp4 (DCP-o-matic could not open the file /path/to/file.mp4 (could not open file /path/to/file.mp4 for reading (-1)).  Perhaps it does not exist or is in an unexpected format.)

If I run the file through FFMPEG in stream copy mode ffmpeg -i file.mp4 -c:v copy -c:a copy out.mp4, the file created by FFMPEG does open in DCP-o-matic correctly. So I guess it's something in the file headers which is causing the problem.

ffprobe output for the file:

ffprobe version 4.2.1 Copyright (c) 2007-2019 the FFmpeg developers
  built with Apple clang version 11.0.0 (clang-1100.0.33.8)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/4.2.1_2 --enable-shared --enable-pthreads --enable-version3 --enable-avresample --cc=clang --host-cflags='-I/Library/Java/JavaVirtualMachines/adoptopenjdk-13.jdk/Contents/Home/include -I/Library/Java/JavaVirtualMachines/adoptopenjdk-13.jdk/Contents/Home/include/darwin -fno-stack-check' --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libmp3lame --enable-libopus --enable-librubberband --enable-libsnappy --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-libsoxr --enable-videotoolbox --disable-libjack --disable-indev=jack
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/path/to/file.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: mp42mp41
    creation_time   : 2019-04-26T08:28:01.000000Z
  Duration: 00:15:43.08, start: 0.000000, bitrate: 30354 kb/s
    Stream #0:0(eng): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 2048x1228, 30032 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
    Metadata:
      creation_time   : 2019-04-26T08:28:01.000000Z
      handler_name    : ?Mainconcept Video Media Handler
      encoder         : AVC Coding
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 317 kb/s (default)
    Metadata:
      creation_time   : 2019-04-26T08:28:01.000000Z
      handler_name    : #Mainconcept MP4 Sound Media Handler

Carl, I'll email you the offending file and the DOM project.

TagsNo tags attached.
Branch
Estimated weeks required
Estimated work required

Activities

overlookmotel

2019-12-07 21:36

developer   ~0003628

NB This is in DCP-o-matic 2.14.8. I've not upgraded to latest yet.

carl

2019-12-10 10:15

administrator   ~0003636

avformat_open_input is failing on the call to s->iformat->read_header(s) around line 639 of libavformat/utils.c

carl

2019-12-10 14:05

administrator   ~0003639

Last edited: 2019-12-10 14:06

Deeper than this it's

int err = parse(c, pb, a);
if (err < 0) {
  c->atom_depth --;
  return err;
}

in mov.c that is raising the error.

carl

2024-01-18 00:10

administrator   ~0006262

Hey! Sadly I don't have this mp4 any more to check, but the ffmpeg you used seems to have been newer than the one bundled with DoM, so perhaps this is just an ffmpeg bug. Let me know if by any chance you still have the file and we can check it out again!

Bug History

Date Modified Username Field Change
2019-12-07 21:35 overlookmotel New Bug
2019-12-07 21:36 overlookmotel Note Added: 0003628
2019-12-10 10:14 carl Assigned To => carl
2019-12-10 10:14 carl Status new => confirmed
2019-12-10 10:15 carl Note Added: 0003636
2019-12-10 14:05 carl Note Added: 0003639
2019-12-10 14:06 carl Note Edited: 0003639
2024-01-18 00:10 carl Status confirmed => resolved
2024-01-18 00:10 carl Resolution open => fixed
2024-01-18 00:10 carl Note Added: 0006262