Opened 10 years ago

Closed 10 years ago

#4159 closed defect (worksforme)

ffprobe exits with "Unsupported codec with id..." error

Reported by: Thanasis Polychronakis Owned by:
Priority: normal Component: ffprobe
Version: 2.4.4 Keywords:
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

Summary of the bug:

Our application handles hundreds of video files produced by the same specific hardware set and uses ffprobe to read the metadata of the files.

We use the the Canon XA25 camera to shoot videos which are then transported to the Teradek cube 155 that streams the video file via NFS to our local server where the ffprobe operation happens.

Out of ~100 files we had 5 failures with ffprobe with the following error message:

Unsupported codec with id 0 for input stream 2

The full output before the this error message is:

ffprobe version 2.4.3 Copyright (c) 2007-2014 the FFmpeg developers
  built on Nov  4 2014 11:01:51 with llvm-gcc 4.2.1 (LLVM build 2336.11.00)
  configuration: --prefix=/Volumes/Ramdisk/sw --enable-gpl --enable-pthreads --enable-version3 --enable-libspeex --enable-libvpx --disable-decoder=libvpx --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-avfilter --enable-libopencore_amrwb --enable-libopencore_amrnb --enable-filters --enable-libgsm --enable-libvidstab --enable-libx265 --arch=x86_64 --enable-runtime-cpudetect
  libavutil      54.  7.100 / 54.  7.100
  libavcodec     56.  1.100 / 56.  1.100
  libavformat    56.  4.101 / 56.  4.101
  libavdevice    56.  0.100 / 56.  0.100
  libavfilter     5.  1.100 /  5.  1.100
  libswscale      3.  0.100 /  3.  0.100
  libswresample   1.  1.100 /  1.  1.100
  libpostproc    53.  0.100 / 53.  0.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Reveal-PCST-120414-122114.mp4':
  Metadata:
    major_brand     : qt  
    minor_version   : 0
    compatible_brands: mobiavc1mp42isom
  Duration: 00:00:24.96, start: 0.000000, bitrate: 2020 kb/s
    Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1963 kb/s, 29.97 fps, 29.97 tbr, 120k tbn, 119.88 tbc (default)
    Metadata:
      handler_name    : AVC Video Handler
      encoder         : AVC Codi
      timecode        : 00:05:14;03
    Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 48 kb/s (default)
    Metadata:
      handler_name    : AAC Audio Handler
    Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
    Metadata:
      handler_name    : TimeCode MediaHdl
      timecode        : 00:05:14;03

As you can see I use the latest stable ffprobe 2.4.3, on osx yosemite.

How to reproduce

Use the attached video file with ffprobe (if attachment fails use this link to download file: http://than.pol.as/Yq8K):

ffprobe Reveal-PCST-120414-122114.mp4

Change History (8)

comment:1 by Thilo Borgmann, 10 years ago

The download link does not work.

comment:2 by Thanasis Polychronakis, 10 years ago

Yes, indeed for some reason it failed to upload on both ends (attachment + my service)

Here is the new clip url: http://than.pol.as/Ypxb and you can download it using this specific url: http://than.pol.as/Ypxb/download/Reveal-PCST-120414-122114.mp4, updating the ticket...

comment:3 by Carl Eugen Hoyos, 10 years ago

Please test current FFmpeg git head. There is nothing unstable about it.

Is the problem you are reporting only reproducible with ffprobe or also with ffmpeg? Only report issues for ffprobe if they are not reproducible with ffmpeg.
I don't see an error message in your original report and I therefore don't understand this ticket currently...

comment:4 by Thanasis Polychronakis, 10 years ago

ffmpeg will properly process the file and the output is readable by ffprobe. However we cannot afford (the cpu / time) to process all the incoming clips so this is not a solution.

I have presented a specific error message and the complete output of ffprobe in my original report.

I have also produced a reliable way to reproduce the issue with the file you can download from here.

If this is the wrong Bug Tracking engine for ffprobe then please show me to the right one.

Last edited 10 years ago by Thanasis Polychronakis (previous) (diff)

comment:5 by Carl Eugen Hoyos, 10 years ago

It is the right bug tracker (you just have to explain that it works with ffmpeg when you report an issue with ffprobe), I just haven't understand yet what your issue is: Afaict no error is shown in your original report and the output if ffprobe looks fine: What is wrong about it?

comment:6 by Thanasis Polychronakis, 10 years ago

You need to be more diligent when reading reports. As I am stating in my original post, the error generated reads:

Unsupported codec with id 0 for input stream 2

The process exits with Code 1 which in turn is propagated in the underlying controlling method in our application and thus the whole operation fails.

We can find multiple workarounds to this issue like downgrading the ffmpeg error to just a warning vs stopping our whole OP but I thought it would be a good idea to bring this to your attention.

in reply to:  6 comment:7 by Carl Eugen Hoyos, 10 years ago

Component: undeterminedffprobe

Replying to thanpolas:

You need to be more diligent when reading reports. As I am stating in my original post, the error generated reads:

Unsupported codec with id 0 for input stream 2

Why did you cut this from your console output?

The process exits with Code 1 which in turn is propagated in the underlying controlling method in our application and thus the whole operation fails.

Did you explain this in your original report?

Did you already test if the issue you see is reproducible with current FFmpeg git head?

comment:8 by Carl Eugen Hoyos, 10 years ago

Resolution: worksforme
Status: newclosed
$ ffprobe Reveal-PCST-120414-122114.mp4
ffprobe version N-68291-g4fa2758 Copyright (c) 2007-2014 the FFmpeg developers
  built on Dec  8 2014 10:45:56 with gcc 4.7 (SUSE Linux)
  configuration: --enable-gpl
  libavutil      54. 15.100 / 54. 15.100
  libavcodec     56. 14.100 / 56. 14.100
  libavformat    56. 15.102 / 56. 15.102
  libavdevice    56.  3.100 / 56.  3.100
  libavfilter     5.  2.103 /  5.  2.103
  libswscale      3.  1.101 /  3.  1.101
  libswresample   1.  1.100 /  1.  1.100
  libpostproc    53.  3.100 / 53.  3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Reveal-PCST-120414-122114.mp4':
  Metadata:
    major_brand     : qt
    minor_version   : 0
    compatible_brands: mobiavc1mp42isom
  Duration: 00:00:24.96, start: 0.000000, bitrate: 2020 kb/s
    Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 1963 kb/s, 29.97 fps, 29.97 tbr, 120k tbn, 119.88 tbc (default)
    Metadata:
      handler_name    : AVC Video Handler
      encoder         : AVC Codi
      timecode        : 00:05:14;03
    Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 48 kb/s (default)
    Metadata:
      handler_name    : AAC Audio Handler
    Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
    Metadata:
      handler_name    : TimeCode MediaHdl
      timecode        : 00:05:14;03
Unsupported codec with id 0 for input stream 2
$ echo $?
0

Please reopen the ticket if I miss something.

Note: See TracTickets for help on using tickets.