[FFmpeg-user] ffserver Unknown VideoCodec: libx264

[Ajay Parashar]

Please find detail logs of ffmpeg as below:

*********************************************************************************************************
ffmpeg -re -i Cars2.mp4 -f mpegts udp://226.0.0.1:1234
ffmpeg version 2.3.3 Copyright (c) 2000-2014 the FFmpeg developers
  built on Sep  3 2014 17:01:53 with gcc 4.8.3 (GCC) 20140624 (Red Hat 4.8.3-1)
  configuration:
  libavutil      52. 92.100 / 52. 92.100
  libavcodec     55. 69.100 / 55. 69.100
  libavformat    55. 48.100 / 55. 48.100
  libavdevice    55. 13.102 / 55. 13.102
  libavfilter     4. 11.100 /  4. 11.100
  libswscale      2.  6.100 /  2.  6.100
  libswresample   0. 19.100 /  0. 19.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Cars2.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    creation_time   : 1970-01-01 00:00:00
    title           : 09--0125--Cars 2 - Trailer - http://www.archive.org/details/09--0125--cars2-Trailer
    encoder         : Lavf52.88.0
    comment         : license:http://creativecommons.org/licenses/by-nd/3.0/
  Duration: 00:01:26.46, start: 0.000000, bitrate: 611 kb/s
    Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 576x240, 510 kb/s, 24 fps, 24 tbr, 24 tbn, 48 tbc (default)
    Metadata:
      creation_time   : 1970-01-01 00:00:00
      handler_name    : VideoHandler
    Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 96 kb/s (default)
    Metadata:
      creation_time   : 1970-01-01 00:00:00
      handler_name    : SoundHandler
Output #0, mpegts, to 'udp://226.0.0.1:1234':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2avc1mp41
    comment         : license:http://creativecommons.org/licenses/by-nd/3.0/
    title           : 09--0125--Cars 2 - Trailer - http://www.archive.org/details/09--0125--cars2-Trailer
    encoder         : Lavf55.48.100
    Stream #0:0(eng): Video: mpeg2video, yuv420p, 576x240, q=2-31, 200 kb/s, 24 fps, 90k tbn, 24 tbc (default)
    Metadata:
      creation_time   : 1970-01-01 00:00:00
      handler_name    : VideoHandler
      encoder         : Lavc55.69.100 mpeg2video
    Stream #0:1(eng): Audio: mp2, 44100 Hz, stereo, s16, 384 kb/s (default)
    Metadata:
      creation_time   : 1970-01-01 00:00:00
      handler_name    : SoundHandler
      encoder         : Lavc55.69.100 mp2
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> mpeg2video (native))
  Stream #0:1 -> #0:1 (aac (native) -> mp2 (native))
Press [q] to stop, [?] for help
frame= 2075 fps= 24 q=31.0 Lsize=    7782kB time=00:01:26.45 bitrate= 737.4kbits/s
video:2797kB audio:4053kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 13.593935%
[lusr at localhost media_files]$



***********************************************************************************************************************
> ffserver says Unknown VideoCodec: libx264, but I assume libx264 is enabled in ffmpeg.
> Please let me know how this issue can be resolved?
> logs of ffserver and ffmpeg as below:

> ffserver version 2.3.3 Copyright (c) 2000-2014 the FFmpeg developers
>   built on Sep  3 2014 17:01:53 with gcc 4.8.3 (GCC) 20140624 (Red Hat 4.8.3-1)
>   configuration:

> ffmpeg version 2.3.3 Copyright (c) 2000-2014 the FFmpeg developers
>   built on Sep  3 2014 17:01:53 with gcc 4.8.3 (GCC) 20140624 (Red Hat 4.8.3-1)
>   configuration:

I don't see --enable-libx264 anywhere in the (empty) configuation line printed by both ffmpeg and ffserver.


The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.