Newest 'libx264' Questions - Stack Overflow

Les articles publiés sur le site

• How to integrate libx264 in ffmpeg for android ?

  5 août 2014, par user3665376

  I am working with integrating ffmpeg for android .

  Since I needed H.264 encoding I need to integrate libx264 with ffmpeg . Given below are the steps I followed .

  1) Build the latest libx264 using android compiler tool-chain to obtain libx264.so.142 .

  2) Build ffmpeg v 2.3 referring to this with --enable -libx264 option while configuring ffmpeg . The method explained in the blog included some editing in configure file of ffmpeg to generate shared object files with extension format [lib name].so rather than the generating shared object file with extension format [lib name].so.[version] (Since android build system supports files with extension .so only).

  The building process was successful but since the generated .so files (after building ffmpeg) has dynamic dependency with libx264.so.142,I need to package libx264.so.142 also with the android .apk file . But since the above format (.so.142) is not supported with android apk building system I cannot package it with the .apk .

  So I think the only option I have is to make some changes in configure file of ffmpeg to change the dynamic dependency of libx264.so.142 to libx264.so . Am I right??

  What changes do I need to make to ffmpeg configure file to achieve this?

• How to integrate shared object file of libx264 while using ffmpeg for android ?

  5 août 2014, par user3665376

  I am working with integrating ffmpeg for android .

  Since I needed H.264 encoding I need to integrate libx264 with ffmpeg . Given below are the steps I followed .

  1) Build the latest libx264 using android compiler tool-chain to obtain libx264.so.142 .

  2) Build ffmpeg v 2.3 referring to this with --enable -libx264 option while configuring ffmpeg . The method explained in the blog included some editing in configure file of ffmpeg to generate shared object files with extension format [lib name].so rather than the generating shared object file with extension format [lib name].so.[version] (Since android build system supports files with extension .so only).

  The building process was successful but since the generated .so files (after building ffmpeg) has dynamic dependency with libx264.so.142,I need to package libx264.so.142 also with the android .apk file . But since the above format (.so.142) is not supported with android apk building system I cannot package it with the .apk .

  So I think the only option I have is to make some changes in configure file of ffmpeg to change the dynamic dependency of libx264.so.142 to libx264.so . Am I right??

  What changes do I need to make to ffmpeg configure file to achieve this?

• Issue #2 when compiling Xuggler for Raspberry pi with libx264

  2 août 2014, par Ashish Sharma

  I am trying to compile Xuggler for Raspberry Pi(Running on Debian OS aka Raspbian),

  I followed the 'Basic Build Instructions' available here for compiling Xuggler.

  After I successfully installed all the prerequisites and set the correct paths, I ran the following command:

  ant run-tests
  

  After sometime I am facing the following error and the ant build fails at libx264:

  {scroll at the end of log to see the issue}

  common/arm/mc-c.c: In function âx264_weight_cache_neonâ:
  common/arm/mc-c.c:89:25: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
  common/arm/mc-c.c:94:25: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
  common/arm/mc-c.c:99:21: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
  common/arm/mc-c.c:101:21: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
  common/arm/mc-c.c: In function âx264_mc_init_armâ:
  common/arm/mc-c.c:236:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
  common/arm/mc-c.c:237:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
  common/arm/mc-c.c:238:19: warning: assignment discards âconstâ qualifier from pointer target type [enabled by default]
  gcc -Wshadow -O3 -fno-fast-math -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include  -Wall -I. -I.  -I'/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include' -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -fPIC -fomit-frame-pointer -fno-tree-vectorize   -c -o common/arm/predict-c.o common/arm/predict-c.c
  as -I/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include  -Wall -I. -I.  -I'/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/stage/home/pi/Downloads/xuggler/include' -std=gnu99 -mcpu=cortex-a8 -mfpu=neon -c -DPIC -DHIGH_BIT_DEPTH=0 -DBIT_DEPTH=8 -o common/arm/cpu-a.o common/arm/cpu-a.S
  as: unrecognized option '-std=gnu99'
  make[1]: *** [common/arm/cpu-a.o] Error 1
  make[1]: Leaving directory `/home/pi/Downloads/xuggle-xuggler/build/native/armv6l-unknown-linux-gnueabihf/captive/libx264/csrc'
  make: *** [all-local] Error 2
  

  I am unable to understand the problem statment "unrecognized option '-std=gnu99'" here, Can someone please tell me how can I resolve this or circumvent it in xuggler?

• How to build ffmpeg with libx264 support for android ?

  30 juillet 2014, par user3665376

  I am working on video editing using ffmpeg in android . I successfully build ffmpeg by following the steps mentioned at here .

  I wanted to integrate libx264 library with ffmpeg for enabling H.264 encoding . Has anybody successful integrating libx264 with android? What all changes I need to make to the configure file or build script to make it compatible with android?

• Get x264 options from stream

  29 juillet 2014, par HardRock

  I have a problem with H264 encoding, actually with libx264 :(

  I want to encode series of images from web camera into h264 and send stream to chines DVR. Problem is DVR can't decode my stream. I tried to adjust (using h264stream_analyzer) SPS and PPS in libx264 to match SPS and PPS headers from "correct stream", produced by other chinese DVR's and IP cameras. But no luck :( Looks like problem in bitstream.

  My stream and "correct" stream - are both may be converted and played with avconv (ffmpeg), for example. Transport is ok. If i send "correct stream" - DVR understand it. Problem in stream.

  One strange thing - "correct stream" contains a lot of 28 and 29 slice types. From h264 specification this is must be "fragmentation" units. But my stream contains only P and I slices, но fragmens.

  So how i can get exact stream encoding parameters from existing sample stream? It may be difference in x264 versions?