Recherche avancée

Sur d’autres sites (8945)

• Android FFmpeg reports "file protocol not found"

  27 avril 2017, par Abdul Mateen

  I am trying to convert sequence images to video using ffmpeg command in android.
  I have build ffmpeg for android and put ffmpeg binary file in /data/local folder.
  I am running ffmpeg command using Runtime.getruntime.execute("mycommand") in Android.

  Stucture of mycommand is like this

  "/data/local/ffmpeg -r 40 qscale 2 -i /mnt/sdcard/images/img%d.jpg /mnt/sdcard/images/finalvideo.mp4" 

  mycommand contains the path of a folder where I placed all my sequence images. Running this command gives me error "protocol not found".

  Also I read that file protocol is default in ffmpeg documentation.

  How can I run such commands ?

  The Error I am getting after running simple command like ffmpeg -i /mnt/sdcard/vid.mp4

  ffmpeg version 0.11.1.git Copyright (c) 2000-2012 the FFmpeg developers
  
  built on Sep 26 2012 11:58:35 with gcc 4.4.3 (GCC)
  
  configuration: --target-os=linux --prefix=/home/esteves/android-ffmpeg --enable-cross-compile --enable-runtime-cpudetect --disable-asm --arch=arm --cc=/home/esteves/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --cross-prefix=/home/esteves/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi- --disable-stripping --nm=/home/esteves/android-ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-nm --sysroot=/home/esteves/android-ndk/platforms/android-8/arch-arm --enable-nonfree --enable-version3 --disable-everything --enable-gpl --disable-doc --enable-avresample --enable-demuxer=amr --enable-demuxer=aac --enable-demuxer=rawvideo --enable-demuxer=rtsp --enable-muxer=rtsp --enable-muxer=flv --enable-muxer=mpegts --enable-muxer=mp4 --enable-demuxer=rtp --enable-demuxer=rtp --disable-ffplay --disable-ffserver --enable-ffmpeg --disable-ffprobe --enable-libx264 --enable-encoder=libx264   libavutil      51. 72.100 / 51. 72.100
  
  libavcodec     54. 55.100 / 54. 55.100
  
  libavformat    54. 25.105 / 54. 25.105
  
  libswscale      2.  1.101 /  2.  1.101
  
  error of main   libswresample   0. 15.100 /  0. 15.100
  
  error of main   libpostproc    52.  0.100 / 52.  0.100
  
  /mnt/sdcard/vid.mp4: Protocol not found

• Visualizing Call Graphs Using Gephi

  1er septembre 2014, par Multimedia Mike — General

  When I was at university studying computer science, I took a basic chemistry course. During an accompanying lab, the teaching assistant chatted me up and asked about my major. He then said, “Computer science ? Well, that’s just typing stuff, right ?”

  My impulsive retort : “Sure, and chemistry is just about mixing together liquids and coming up with different colored liquids, as seen on the cover of my high school chemistry textbook, right ?”

  
  
  

  In fact, pure computer science has precious little to do with typing (as is joked in CS circles, computer science is about computers in the same way that astronomy is about telescopes). However, people who study computer science often pursue careers as programmers, or to put it in fancier professional language, software engineers.

  So, what’s a software engineer’s job ? Isn’t it just typing ? That’s where I’ve been going with this overly long setup. After thinking about it for long enough, I like to say that a software engineer’s trade is managing complexity.

  A few years ago, I discovered Gephi, an open source tool for graph and data visualization. It looked neat but I didn’t have much use for it at the time. Recently, however, I was trying to get a better handle on a large codebase. I.e., I was trying to manage the project’s complexity. And then I thought of Gephi again.

  Prior Work
  One way to get a grip on a large C codebase is to instrument it for profiling and extract details from the profiler. On Linux systems, this means compiling and linking the code using the -pg flag. After running the executable, there will be a gmon.out file which is post-processed using the gprof command.

  GNU software development tools have a reputation for being rather powerful and flexible, but also extremely raw. This first hit home when I was learning how to use the GNU tool for code coverage — gcov — and the way it outputs very raw data that you need to massage with other tools in order to get really useful intelligence.

  And so it is with gprof output. The output gives you a list of functions sorted by the amount of processing time spent in each. Then it gives you a flattened call tree. This is arranged as “during the profiled executions, function c was called by functions a and b and called functions d, e, and f ; function d was called by function c and called functions g and h”.

  How can this call tree data be represented in a more instructive manner that is easier to navigate ? My first impulse (and I don’t think I’m alone in this) is to convert the gprof call tree into a representation suitable for interpretation by Graphviz. Unfortunately, doing so tends to generate some enormous and unwieldy static images.

  Feeding gprof Data To Gephi
  I learned of Gephi a few years ago and recalled it when I developed an interest in gaining better perspective on a large base of alien C code. To understand what this codebase is doing for a particular use case, instrument it with gprof, gather execution data, and then study the code paths.

  How could I feed the gprof data into Gephi ? Gephi supports numerous graphing formats including an XML-based format named GEXF.

  Thus, the challenge becomes converting gprof output to GEXF.

  Which I did.

  Demonstration
  I have been absent from FFmpeg development for a long time, which is a pity because a lot of interesting development has occurred over the last 2-3 years after a troubling period of stagnation. I know that 2 big video codec developments have been HEVC (next in the line of MPEG codecs) and VP9 (heir to VP8’s throne). FFmpeg implements them both now.

  I decided I wanted to study the code flow of VP9. So I got the latest FFmpeg code from git and built it using the options "--extra-cflags=-pg --extra-ldflags=-pg". Annoyingly, I also needed to specify "--disable-asm" because gcc complains of some register allocation snafus when compiling inline ASM in profiling mode (and this is on x86_64). No matter ; ASM isn’t necessary for understanding overall code flow.

  After compiling, the binary ‘ffmpeg_g’ will have symbols and be instrumented for profiling. I grabbed a sample from this VP9 test vector set and went to work.

  ./ffmpeg_g -i vp90-2-00-quantizer-00.webm -f null /dev/null
  gprof ./ffmpeg_g > vp9decode.txt
  convert-gprof-to-gexf.py vp9decode.txt > /bigdisk/vp9decode.gexf
  

  Gephi loads vp9decode.gexf with no problem. Using Gephi, however, can be a bit challenging if one is not versed in any data exploration jargon. I recommend this Gephi getting starting guide in slide deck form. Here’s what the default graph looks like :

  
  
  

  Not very pretty or helpful. BTW, that beefy arrow running from mid-top to lower-right is the call from decode_coeffs_b -> iwht_iwht_4x4_add_c. There were 18774 from the former to the latter in this execution. Right now, the edge thicknesses correlate to number of calls between the nodes, which I’m not sure is the best representation.

  Following the tutorial slide deck, I at least learned how to enable the node labels (function symbols in this case) and apply a layout algorithm. The tutorial shows the force atlas layout. Here’s what the node neighborhood looks like for probing file type :

  
  
  

  Okay, so that’s not especially surprising– avprobe_input_format3 calls all of the *_probe functions in order to automatically determine input type. Let’s find that decode_coeffs_b function and see what its neighborhood looks like :

  
  
  

  That’s not very useful. Perhaps another algorithm might help. I select the Fruchterman–Reingold algorithm instead and get a slightly more coherent representation of the decoding node neighborhood :

  
  
  

  Further Work
  Obviously, I’m just getting started with this data exploration topic. One thing I would really appreciate in such a tool is the ability to interactively travel the graph since that’s what I’m really hoping to get out of this experiment– watching the code flows.

  Perhaps someone else can find better use cases for visualizing call graph data. Thus, I have published the source code for this tool at Github.

• arm-linux-androideabi-gcc is unable to create an executable - compile ffmpeg for android armeabi devices

  25 juillet 2013, par Chaitanya Chandurkar

  I am trying to compile ffmpeg for android armeabi devices.
  I am following tutorial by roman10.net
  His given build script builds ffmpeg for armv7-a devices. I want to build it for armeabi.
  

  My ultimate aim is to run ffmpeg commands on android armeabi and armv7-a devices.

  So i change the script's CPU part from

  #arm v7vfpv3
  
  CPU=armv7-a
  
  OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfpv3-d16 -marm -march=$CPU "
  
  PREFIX=./android/$CPU
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  build_one 

  to

  #arm v6
  
  CPU=armv6
  
  OPTIMIZE_CFLAGS="-marm -march=$CPU"
  
  PREFIX=./android/$CPU 
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  build_one

  (I thought changing it to armv6 would build ffmpeg compatible with armeabi devices. m i wrong ?)

  Doubt 1 :
  Do i also have to change toolchain ?
  i.e from arm-linux-androideabi-4.4.3 to arm-eabi-4.4.0 ?????

  Doubt 2 :

  When i try running ./build.sh (without changing toolchain) it gives me following error :
  

  /home/chaitanya/android/android-ndk-r5b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc is unable to create an executable file.
  
  C compiler test failed.
  
  
  
  If you think configure made a mistake,.. blaah blahh blaah

  after that i got lot of warnings saying :
  ‘sub_id’ is deprecated and many other function deprecated warnings.

  platform : ubuntu 11.10
  ffmpeg version : 0.11.2
  NDK : android-ndk-r5b

  Here is my build script :

  #!/bin/bash
  
  ######################################################
  
  # Usage:
  
  # put this script in top of FFmpeg source tree
  
  # ./build_android
  
  # It generates binary for following architectures:
  
  # ARMv6 
  
  # ARMv6+VFP 
  
  # ARMv7+VFM-ïd16 (Tegra2) 
  
  # ARMv7+Neon (Cortex-A8)
  
  # Customizing:
  
  # 1. Feel free to change ./configure parameters for more features
  
  # 2. To adapt other ARM variants
  
  # set $CPU and $OPTIMIZE_CFLAGS 
  
  # call build_one
  
  ######################################################
  
  NDK=~/android/android-ndk-r5b
  
  PLATFORM=$NDK/platforms/android-8/arch-arm/
  
  PREBUILT=$NDK/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86
  
  function build_one
  
  {
  
  ./configure --target-os=linux \
  
      --prefix=$PREFIX \
  
      --enable-cross-compile \
  
      --extra-libs="-lgcc" \
  
      --arch=arm \
  
      #--cc=$PREBUILT/bin/arm-linux-androideabi-gcc \
  
      --cross-prefix=$PREBUILT/bin/arm-linux-androideabi- \
  
      #--nm=$PREBUILT/bin/arm-linux-androideabi-nm \
  
      --sysroot=$PLATFORM \
  
      --extra-cflags=" -O3 -fpic -DANDROID -DHAVE_SYS_UIO_H=1 -Dipv6mr_interface=ipv6mr_ifindex -fasm -Wno-psabi -fno-short-enums -fno-strict-aliasing -finline-limit=300 $OPTIMIZE_CFLAGS " \
  
      --disable-shared \
  
      --enable-static \
  
      --extra-ldflags="-Wl,-rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib -nostdlib -lc -lm -ldl -llog" \
  
      --disable-everything \
  
      --enable-demuxer=mov \
  
      --enable-demuxer=h264 \
  
      --disable-ffplay \
  
      --enable-protocol=file \
  
      --enable-avformat \
  
      --enable-avcodec \
  
      --enable-decoder=rawvideo \
  
      --enable-decoder=mjpeg \
  
      --enable-decoder=h263 \
  
      --enable-decoder=mpeg4 \
  
      --enable-decoder=h264 \
  
      --enable-parser=h264 \
  
      --disable-network \
  
      --enable-zlib \
  
      --disable-avfilter \
  
      --disable-avdevice \
  
      $ADDITIONAL_CONFIGURE_FLAG
  
  
  
  make clean
  
  make  -j4 install
  
  $PREBUILT/bin/arm-linux-androideabi-ar d libavcodec/libavcodec.a inverse.o
  
  $PREBUILT/bin/arm-linux-androideabi-ld -rpath-link=$PLATFORM/usr/lib -L$PLATFORM/usr/lib  -soname libffmpeg.so -shared -nostdlib  -z,noexecstack -Bsymbolic --whole-archive --no-undefined -o $PREFIX/libffmpeg.so libavcodec/libavcodec.a libavformat/libavformat.a libavutil/libavutil.a libswscale/libswscale.a -lc -lm -lz -ldl -llog  --warn-once  --dynamic-linker=/system/bin/linker $PREBUILT/lib/gcc/arm-linux-androideabi/4.4.3/libgcc.a
  
  }
  
  
  
  #arm v6
  
  CPU=armv6
  
  OPTIMIZE_CFLAGS="-marm -march=$CPU"
  
  PREFIX=./android/$CPU 
  
  ADDITIONAL_CONFIGURE_FLAG=
  
  build_one
  
  
  
  #arm v7vfpv3
  
  #CPU=armv7-a
  
  #OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfpv3-d16 -marm -march=$CPU "
  
  #PREFIX=./android/$CPU
  
  #ADDITIONAL_CONFIGURE_FLAG=
  
  #build_one
  
  
  
  #arm v7vfp
  
  #CPU=armv7-a
  
  #OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=vfp -marm -march=$CPU "
  
  #PREFIX=./android/$CPU-vfp
  
  #ADDITIONAL_CONFIGURE_FLAG=
  
  #build_one
  
  
  
  #arm v7n
  
  #CPU=armv7-a
  
  #OPTIMIZE_CFLAGS="-mfloat-abi=softfp -mfpu=neon -marm -march=$CPU -mtune=cortex-a8"
  
  #PREFIX=./android/$CPU 
  
  #ADDITIONAL_CONFIGURE_FLAG=--enable-neon
  
  #build_one
  
  
  
  #arm v6+vfp
  
  #CPU=armv6
  
  #OPTIMIZE_CFLAGS="-DCMP_HAVE_VFP -mfloat-abi=softfp -mfpu=vfp -marm -march=$CPU"
  
  #PREFIX=./android/${CPU}_vfp 
  
  #ADDITIONAL_CONFIGURE_FLAG=
  
  #build_one

  How do i tackle this problem ? what is going wrong ?