Recherche avancée

Sur d’autres sites (7690)

• Compile ffmpeg with x264 shows : ERROR : libx264 not found

  6 mai 2019, par NKam

  Trying to install ffmpeg from source with libx264 package. When I compile ffmpeg can’t find x264 because it is not installed.
  I followed ffmpeg installation guide.

  I tried to install and compile ffmpeg locally and found out in folder ffmpeg_build/include I don’t have x264 files installed.

  To compile libx264 I used :

  cd /ffmpeg_sources &&

  git -C x264 pull 2> /dev/null || git clone —depth 1 https://code.videolan.org/videolan/x264.git &&

  cd x264 &&

  PATH="$HOME/bin :$PATH"

  PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig" ./configure —prefix="$HOME/ffmpeg_build" —bindir="$HOME/bin" —enable-static —enable-pic &&

  PATH="$HOME/bin :$PATH" make &&

  make install

  I changed url to https://code.videolan.org/videolan/x264.git, because this url https://git.videolan.org/git/x264 from guide not working

  Here how config.log’s last lines look like

  test_cflags -Wmaybe-uninitialized
  
  test_cc -Wmaybe-uninitialized
  
  BEGIN /tmp/ffconf.1LD1vklR/test.c
  
      1   int x;
  
  END /tmp/ffconf.1LD1vklR/test.c
  
  gcc -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC -I/home/nurs/ffmpeg_build/include -std=c11 -fomit-frame-pointer -fPIC -pthread -I/home/nurs/ffmpeg_build/include -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/fribidi -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/opus -I/usr/include/opus -I/usr/include/alsa -g -Wdeclaration-after-statement -Wall -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wwrite-strings -Wtype-limits -Wundef -Wmissing-prototypes -Wno-pointer-to-int-cast -Wstrict-prototypes -Wempty-body -Wno-parentheses -Wno-switch -Wno-format-zero-length -Wno-pointer-sign -Wno-unused-const-variable -Wno-char-subscripts -O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize -Werror=format-security -Werror=implicit-function-declaration -Werror=missing-prototypes -Werror=return-type -Werror=vla -Wformat -fdiagnostics-color=auto -Wmaybe-uninitialized -c -o /tmp/ffconf.1LD1vklR/test.o /tmp/ffconf.1LD1vklR/test.c

  I want to know what I missed. I want ffmpeg to find x264, if it is not installed how can I find way to install.

• Scale image with ffmpeg in bash script

  17 juin 2014, par Brian Bennett

  I’m playing with jclem’s Gifify bash script as a quick way to make GIFs for documentation. It runs on ffmpeg and ImageMagick and I’m trying to find a way to add a variable to scale the produced GIF so I don’t have to go back and add it again. I thought I added the d (resize) variable correctly, but the script fails and just prints the help contents. It does not show my added variable in that help readout. Any ideas ?

  Update

  I solved the problem with printing help contents rather than running the script, but now I’m receiving an error about the -scale parameter.

  convert: invalid argument for option `-scale': -vf @ error/convert.c/ConvertImageCommand/2513.

  Is this because of my if statement syntax for the scale parameter below ?

  #!/bin/bash
  
  
  
  function printHelpAndExit {
  
    echo 'Usage:'
  
    echo '  gifify -conx filename'
  
    echo ''
  
    echo 'Options: (all optional)'
  
    echo '  c CROP:   The x and y crops, from the top left of the image, i.e. 640:480'
  
    echo '  o OUTPUT: The basename of the file to be output (default "output")'
  
    echo '  n:        Do not upload the resulting image to CloudApp'
  
    echo '  r FPS:    Output at this (frame)rate (default 10)'
  
    echo '  s SPEED:  Output using this speed modifier (default 1)'
  
    echo '            NOTE: GIFs max out at 100fps depending on platform. For consistency,'
  
    echo '            ensure that FPSxSPEED is not > ~60!'
  
    echo '  x:        Remove the original file and resulting .gif once the script is complete'
  
    echo '  d SCALE:  Scales GIF image to specified dimensions (default no scale)'
  
    echo ''
  
    echo 'Example:'
  
    echo '  gifify -c 240:80 -o my-gif -x my-movie.mov'
  
    exit $1
  
  }
  
  
  
  noupload=0
  
  fps=10
  
  speed=1
  
  
  
  OPTERR=0
  
  
  
  while getopts "c:o:r:s:d:nx" opt; do
  
    case $opt in
  
      c) crop=$OPTARG;;
  
      h) printHelpAndExit 0;;
  
      o) output=$OPTARG;;
  
      n) noupload=1;;
  
      r) fps=$OPTARG;;
  
      s) speed=$OPTARG;;
  
      x) cleanup=1;;
  
      d) scale=$OPTARG;;
  
      *) printHelpAndExit 1;;
  
    esac
  
  done
  
  
  
  shift $(( OPTIND - 1 ))
  
  
  
  filename=$1
  
  
  
  if [ -z ${output} ]; then
  
    output=$filename
  
  fi
  
  
  
  if [ -z $filename ]; then printHelpAndExit 1; fi
  
  
  
  if [ $crop ]; then
  
    crop="-vf crop=${crop}:0:0"
  
  else
  
    crop=
  
  fi
  
  
  
  if [ $scale ]; then
  
    scale="-vf scale=${scale}:0:0"
  
  else
  
    scale=
  
  fi
  
  
  
  # -delay uses time per tick (a tick defaults to 1/100 of a second)
  
  # so 60fps == -delay 1.666666 which is rounded to 2 because convert
  
  # apparently stores this as an integer. To animate faster than 60fps,
  
  # you must drop frames, meaning you must specify a lower -r. This is
  
  # due to the GIF format as well as GIF renderers that cap frame delays
  
  # < 3 to 3 or sometimes 10. Source:
  
  # http://humpy77.deviantart.com/journal/Frame-Delay-Times-for-Animated-GIFs-214150546
  
  echo 'Exporting movie...'
  
  delay=$(bc -l <<< "100/$fps/$speed")
  
  temp=$(mktemp /tmp/tempfile.XXXXXXXXX)
  
  
  
  ffmpeg -loglevel panic -i $filename $crop -r $fps -f image2pipe -vcodec ppm - >> $temp
  
  
  
  echo 'Making gif...'
  
  cat $temp | convert +dither -layers Optimize -delay $delay -scale $scale - ${output}.gif
  
  
  
  if [ $noupload -ne 1 ]; then
  
    open -a Cloud ${output}.gif
  
  
  
    echo `pbpaste`
  
  
  
    if [ $cleanup ]; then
  
      rm $filename
  
      rm ${output}.gif
  
    fi
  
  else
  
    echo ${output}.gif
  
  fi

• UnsatisfiedLinkError for armeabi with Android Studio on Ubuntu but with Android Studio on Windows it works

  14 juillet 2015, par dddog

  I’m working at an Android app that uses ffmpeg-android-arm.jar who contains native libs for video/audio encoding.
  My native libs are included in the project by copying the ffmpeg-android-arm.jar in the app/libs folder. ffmpeg-android-arm.jar is just an archive having the following folder structure lib/armeabi/ and in the armeabi folder being all the native libs as .so files.

  Building the apk using Android Studio on Windows 8 works just fine, the statement bellow, being the first that wants to load a native library working well.

  //neon library optimized for opencv
  
  static {
  
      Log.d(TAG, "about to load library checkneon...");
  
      try {
  
          System.loadLibrary("checkneon");
  
      } catch (Exception e) {
  
          e.printStackTrace();
  
      } catch (Error error) {
  
          error.printStackTrace(System.out);
  
      }
  
      Log.d(TAG, "library checkneon loaded!");
  
  }

  Going on Android Studio running on Ubuntu 14.04.02, I’m unable to make my project run, as I keep receiving java.lang.UnsatisfiedLinkError. See the stack trace bellow :

  07-14 20:41:05.616  17018-17018/? D/dalvikvm﹕ Late-enabling CheckJNI
  
  07-14 20:41:05.786  17018-17018/org.myfrogvrvp8 D/RecordActivity﹕ about to load library checkneon...
  
  07-14 20:41:05.786  17018-17018/org.myfrogvrvp8 I/System.out﹕ java.lang.UnsatisfiedLinkError: Couldn't load checkneon from loader dalvik.system.PathClassLoader[dexPath=/data/app/org.myfrogvrvp8-2.apk,libraryPath=/data/app-lib/org.myfrogvrvp8-2]: findLibrary returned null
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.Runtime.loadLibrary(Runtime.java:355)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.System.loadLibrary(System.java:525)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at org.myfrogvrvp8.FFmpegRecorderActivity.<clinit>(FFmpegRecorderActivity.java:189)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.Class.newInstanceImpl(Native Method)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.Class.newInstance(Class.java:1130)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.Instrumentation.newActivity(Instrumentation.java:1078)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2210)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2349)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.ActivityThread.access$700(ActivityThread.java:159)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1316)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.os.Handler.dispatchMessage(Handler.java:99)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.os.Looper.loop(Looper.java:176)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at android.app.ActivityThread.main(ActivityThread.java:5419)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.reflect.Method.invokeNative(Native Method)
  
  07-14 20:41:05.791  17018-17018/org.myfrogvrvp8 I/System.out﹕ at java.lang.reflect.Method.invoke(Method.java:525)
  
  07-14 20:41:05.796  17018-17018/org.myfrogvrvp8 I/System.out﹕ at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1046)
  
  07-14 20:41:05.796  17018-17018/org.myfrogvrvp8 I/System.out﹕ at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:862)
  
  07-14 20:41:05.796  17018-17018/org.myfrogvrvp8 I/System.out﹕ at dalvik.system.NativeStart.main(Native Method)
  
  </clinit>

  I’ve checked both apks, and they both have the native .so files included in the lib/armeabi folder.

  I’m quite puzzled...
  Any help much appreciated !