Recherche avancée

Sur d’autres sites (8799)

• Configured Half-ninja android FFMPEG project

  24 décembre 2013, par Mr.G

  I have configured android-halfninja project completely and i manage to build

  refered to this link

  libs/armeabi/libvideokit.so and
  libs/armeabi/ffmpeg

  libs from the given source

  But i had to make some changes to the .sh files in order to build .so files.

  But now i tried to execute following ffmpeg command in my android project it doesn't run properly

      String var[] = {"ffmpeg","-i",input};
  
  
  
  
  
  
  
  12-24 10:34:44.569: I/VideoKit(14374): Loading native library compiled at 14:43:51 Dec 18 2013
  
  12-24 10:34:44.599: I/ActivityManager(290): Process uk.co.halfninja.videokit (pid 14374) has died.
  
  12-24 10:34:44.599: W/ActivityManager(290): Force removing ActivityRecord{2bea3e28 uk.co.halfninja.videokit/.MainActivity}: app died, no saved state

  Can any one tell me what might be th issue to have this error in half-nonja project

  here is my configure_ffmpeg.sh file

      #!/bin/bash
  
  pushd `dirname $0`
  
  . settings.sh
  
  
  
  if [[ $DEBUG == 1 ]]; then
  
    echo "DEBUG = 1"
  
    DEBUG_FLAG="--disable-stripping"
  
  fi
  
  
  
  # I haven't found a reliable way to install/uninstall a patch from a Makefile,
  
  # so just always try to apply it, and ignore it if it fails. Works fine unless
  
  # the files being patched have changed, in which cause a partial application
  
  # could happen unnoticed.
  
  patch -N -p1 --reject-file=- < redact-plugins.patch
  
  patch -N -p1 --reject-file=- < arm-asm-fix.patch
  
  patch -d ffmpeg -N -p1 --reject-file=- < \
  
      ARM_generate_position_independent_code_to_access_data_symbols.patch
  
  patch -d ffmpeg -N -p1 --reject-file=- < \
  
      ARM_intmath_use_native-size_return_types_for_clipping_functions.patch
  
  patch -d ffmpeg -N -p1 --reject-file=- < \
  
      enable-fake-pkg-config.patch
  
  
  
  pushd ffmpeg
  
  
  
  ./configure \
  
  $DEBUG_FLAG \
  
  --arch=arm \
  
  --cpu=cortex-a8 \
  
  --target-os=linux \
  
  --enable-runtime-cpudetect \
  
  --prefix=$prefix \
  
  --enable-pic \
  
  --disable-shared \
  
  --enable-static \
  
  --cross-prefix=$NDK_TOOLCHAIN_BASE/bin/$NDK_ABI-linux-androideabi- \
  
  --sysroot="$NDK_SYSROOT" \
  
  --extra-cflags="-I../x264 -mfloat-abi=softfp -mfpu=neon" \
  
  --extra-ldflags="-L../x264" \
  
  \
  
  --enable-version3 \
  
  --enable-gpl \
  
  \
  
  --disable-doc \
  
  --enable-yasm \
  
  \
  
  --disable-everything \
  
  --enable-decoder=mjpeg \
  
  --enable-demuxer=mjpeg \
  
  --enable-parser=mjpeg \
  
  --enable-demuxer=image2 \
  
  --enable-muxer=mp4 \
  
  --enable-encoder=libx264 \
  
  --enable-decoder=rawvideo \
  
  --enable-protocol=file \
  
  --enable-hwaccels \
  
  --enable-filter=buffer \
  
  --enable-filter=buffersink \
  
  --disable-demuxer=v4l \
  
  --disable-demuxer=v4l2 \
  
  --disable-indev=v4l \
  
  --disable-indev=v4l2 \
  
  \
  
  --disable-indevs \
  
  --enable-indev=lavfi \
  
  --disable-outdevs \
  
  \
  
  --enable-hwaccels \
  
  \
  
  --disable-ffmpeg \
  
  --disable-ffplay \
  
  --disable-ffprobe \
  
  --disable-ffserver \
  
  --disable-network \
  
  \
  
  --enable-libx264 \
  
  --enable-zlib \
  
  --enable-muxer=md5
  
  
  
  popd; popd
  
  
  
  
  
  #--enable-decoders \
  
  #--enable-encoders \
  
  #--enable-muxers \
  
  #--enable-demuxers \
  
  #--enable-parsers \
  
  #--enable-protocols \
  
  #--enable-filter=buffer \
  
  #--enable-filter=buffersink \
  
  #--enable-avresample \
  
  #--enable-faac \

• How can I analyze file and detect if the file is in H.264 video format ? [on hold]

  5 octobre 2016, par codeDom

  I write software C/C++ to recover deleted files, and I need to identify files according to their binary content, so my question is there a simple way to know if a particular file is H.264 format video ? is H.264 has an signature ?

  I saw the code of FFMPEG here, but can it help me, how ?

• Track format difference when importing BMP file into quicktime .mov file

  23 juillet 2015, par Neal Davis

  I am creating a quicktime container .mov file from one BMP file in two ways :

  1. Using the quicktime COM object API for .NET C# under windows
  2. Using ffmpeg command line (rawvideo codec)

  Both resulting .MOV files open with Quicktime Player Pro just fine and look identical to my eyes, also they are either the same size as the original BMP or larger.

  However, when viewing the track properties under QT Player PRO, they show :

  1. track format = BMP.
  2. track format = NONE.

  Is there likely a difference since in 1. above I do not set a track properties format ? In other words, is there likely any changes being made to the BMP bits in number 1 above (like compression, or alpha, or ???) ?