The file could not be transcoded because the video codec is not supported

what does admin/config/ffmpeg_wrapper say about your installed codecs?

Can you try running the conversion you want to do on the command line and see if it works? Something like:
/usr/local/bin/ffmpeg -i "/tmp/test_1.mp4" test.flv

I'm having the same issue.

Using ffmpeg from the command line works perfectly fine, but ffmpeg_wrapper keeps giving me the "The file could not be transcoded because the video codec is not supported" error.

I'm using ffmpeg version N-31422-g45ecc7a.

@ronin17 are codecs showing in admin/config/ffmpeg_wrapper?

Try setting can_decode_file() to return TRUE. If that works then it is likely an issue with how the codecs are being detected.

I think I may have tracked this down to a change that I made to how ffmpeg reports back "not available". The function was checking for 'na' instead of 'N/A' which is the new way that ffmpeg returns data. Please give the dev version a try again.

The interesting line is:

Stream #0.1(eng): Video: h264 (High), yuv420p, 720x480 [PAR 8:9 DAR 4:3], 2535 kb/s, 29.97 fps, 29.97 tbr, 1001 tbn, 59.94 tbc

The function get_file_data($filepath) will determine a codec called "h264 (High)". But in the codec list from get_formats() will be only a codec called "h264".

I have the same problem with the codec "h264 (Main)" in my local machine (using Mac ports, ffmpeg version 0.7.1). I thought about adding the following to get_file_data():

      // Not sure if it is a bug of ffmpeg, but it showed the codec h264 (Main),
      // instead of h264, see issue on drupal.org/node/1215400.
      $video_codec_exceptions = array(
        'h264 (Main)' => 'h264',
        'h264 (High)' => 'h264',
      );
      // Set the correct codec name.
      $file['video']['codec'] = $video_codec_exceptions[$file['video']['codec']];

How much exceptions will there be? How many surprises will ffmpeg have for us? I guess I need to dive in the ffmpeg documentation.

Another way would be to fix the regex to only read the first word, because in the codec list aren't codecs with spaces.

Added the patch for the quick workaround.

I think the best is to modify the regex, to just take the first word as codec. I saw codecs with letters and digits and underscore but nothing else, not hyphen and no space in the name.

There are a lot of different h264 profiles: http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Profiles. Recently I got "h264 (Constrained Baseline)". Let's fix this with an regex. But I don't kow, which one to touch.

If this applies to all of them, maybe use this:

      // Ffmpeg shows the codec h264 followed by a space and the profile name in
      // parenthesis, i.e. "h264 (Main)". Extract only the codec, i.e. h264.
      // See issue on drupal.org/node/1215400.
      if (preg_match('/([^\s]+).*/', $file['video']['codec'], $matches)) {
        // Set the correct codec name.
        $file['video']['codec'] = $matches[1];
      }

@osopolar yes I've seen this as well on recent versions of ffmpeg and accompanying libraries. I'm not sure if it is safe to assume that the text in the parentheses is safe to ignore, but I don't know if there is another choice.

I think your patch is a good idea but I think it needs to be moved up into the main if/else statement because otherwise $ffmpeg->errors is still going to be set.

The codec is detected well, but it is named "h264 (Main)" instead of just "h264". Later we the module is comparing the name of the video codec with the codec list of ffmpeg and won't find it.

I guess there should be something written in the ffmpeg specifications, but currently I don't have time to research.

Tracking

how to convert wmv file