[FFmpeg-user] libx264 vs android 4.4

Carl Eugen Hoyos cehoyos at ag.or.at
Wed Jul 16 14:56:10 CEST 2014

Patrick Shirkey <pshirkey <at> boosthardware.com> writes:

> ffmpeg -f fbdev -r 1 -i /dev/graphics/fb0 -vcodec libx264 
> -f h264 -preset:v slow -pix_fmt yuv420p 
> http://localhost:8090/feed1.ffm

I don't know your use case but I wonder if a faster 
preset with a higher frame rate wouldn't be more 

(I haven't used ffm for a long time but are you sure 
that -f h286 feed.ffm works? Maybe you meant -f h264 
feed.h264? Which makes the -f h264 superfluous.)

>   configuration: --arch=arm --target-os=linux --enable-cross-compile
> --cross-prefix=/4.4/prebuilts/gcc/linux-x86/arm/
> arm-linux-androideabi-4.7/bin/arm-linux-androideabi-
> --sysroot=/4.4/prebuilts/ndk/current/platforms/android-18/arch-arm
> --enable-gpl --enable-avresample --enable-libx264 --enable-ffplay
> --extra-cflags='-fno-builtin-sin -fno-builtin-sinf -I/4.4/external/x264'
> --extra-ldflags=-L/4.4/external/x264

As said --enable-ffplay has no effect (and it does not 
tell you if it didn't work), so please remove it.

I don't think you want to use --enable-avresample.

You wrote in an earlier email:
> [--cpu] doesn't appear to have any affect for
> this build.

Do you mean the output is bitexact with and without 
the --cpu option? Or that you did some performance 
tests and couldn't reproduce a difference?
It cannot make a difference for the usecase above 
(that only depends on libx264 compilation / speed) 
but generally, I thought the --cpu option is useful 
for arm.

Carl Eugen

More information about the ffmpeg-user mailing list