Recherche avancée

Sur d’autres sites (13979)

• How to solve bad instruction `vadd.i16 q0,q0,q0' when attempting to check gcc for neon instruction

  6 juillet 2012, par newentry

  Checking  gcc supports failed for neon instruction vadd.i16 q0,q0,q0
  
      test.c
  
  
  
      int main ()
  
      {
  
       __asm__("vadd.i16 q0, q0, q0"); return 0;
  
      }
  
  
  
      arm-linux-androideabi-gcc test.c
  
      /tmp/ccfc8m0G.s: Assembler messages:
  
      /tmp/ccfc8m0G.s:24: Error: bad instruction `vadd.i16 q0,q0,q0'

  Tried with flags -mcpu=cortex-a8 -mfpu=neon but stil no success

  Above code was used to test gcc support for neon instruction.

  Actually i am trying to build x264 with NEON support for ARM platformAfter running configure script
  x264 config log file contains

  Command line options : "—cross-prefix=arm-linux-androideabi-" "—enable-pic" "—extra- cflags=-mcpu=cortex-a8" "—host=arm-linux"

  checking whether arm-linux-androideabi-gcc works... yes
  
  checking whether arm-linux-androideabi-gcc supports for( int i = 0; i < 9; i++ ); with -std=gnu99... yes
  
  checking whether arm-linux-androideabi-gcc supports __asm__("rev ip, ip");... yes
  
  checking whether arm-linux-androideabi-gcc supports __asm__("movt r0, #0");... yes
  
  checking whether arm-linux-androideabi-gcc supports __asm__("vadd.i16 q0, q0, q0");... no
  
  
  
  arm-linux-androideabi-gcc conftest.c  -Wall -I. -I$(SRCPATH) -mcpu=cortex-a8 -std=gnu99    -lm -o conftest
  
  E:\cygwin\tmp\ccVtVI1i.s: Assembler messages:
  
  E:\cygwin\tmp\ccVtVI1i.s:24: Error: bad instruction `vadd.i16 q0,q0,q0'
  
  --------------------------------------------------
  
  Failed program was:
  
  --------------------------------------------------
  
  int main () { __asm__("vadd.i16 q0, q0, q0"); return 0; }
  
  --------------------------------------------------
  
  
  
  
  
  config.h contains
  
  
  
  #define HAVE_MALLOC_H 1
  
  #define HAVE_ARMV6 1
  
  #define HAVE_ARMV6T2 1
  
  #define ARCH_ARM 1
  
  #define SYS_LINUX 1
  
  #define HAVE_VECTOREXT 1
  
  #define fseek fseeko
  
  #define ftell ftello
  
  #define HAVE_GPL 1
  
  #define HAVE_INTERLACED 1
  
  #define HAVE_ALTIVEC 0
  
  #define HAVE_ALTIVEC_H 0
  
  #define HAVE_MMX 0
  
  #define HAVE_NEON 0
  
  #define HAVE_BEOSTHREAD 0
  
  #define HAVE_POSIXTHREAD 0
  
  #define HAVE_WIN32THREAD 0
  
  #define HAVE_THREAD 0
  
  #define HAVE_LOG2F 0
  
  #define HAVE_VISUALIZE 0
  
  #define HAVE_SWSCALE 0
  
  #define HAVE_LAVF 0
  
  #define HAVE_FFMS 0
  
  #define HAVE_GPAC 0
  
  #define HAVE_GF_MALLOC 0
  
  #define HAVE_AVS 0
  
  #define HAVE_CPU_COUNT 0
  
  
  
  
  
  Running make command build x264 static lib  based on above config.h which contains HAVE_NEON 0
  
  
  
  
  
  **Compiler Version**
  
  
  
  
  
  
  
  arm-linux-androideabi-gcc -v
  
  Using built-in specs.
  
  Target: arm-linux-androideabi
  
  Configured with: /tmp/ndk-digit/src/build/../gcc/gcc-4.4.3/configure --prefix=/usr/local/google/digit/repo/opensource/ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/windows --target=arm-linux-androideabi --host=i586-mingw32msvc --build=x86_64-linux-gnu --with-gnu-as --with-gnu-ld --enable-languages=c,c++ --with-gmp=/tmp/ndk-digit/build/toolchain/temp-install --with-mpfr=/tmp/ndk-digit/build/toolchain/temp-install --disable-libssp --enable-threads --disable-nls --disable-libmudflap --disable
  
  -libgomp --disable-libstdc__-v3 --disable-sjlj-exceptions --disable-shared --disable-tls --with-float=soft --with-fpu=vfp --with-arch=armv5te --enable-target-optspace --enable-initfini-array --disable-nls --prefix=/usr/local/google/digit/repo/opensource/ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/windows --with-sysroot=/usr/local/google/digit/repo/opensource/ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/windows/sysroot --with-binutils-version=2.20.1 --with-mpfr-version=2.4.1 --with
  
  -gmp-version=4.2.4 --with-gcc-version=4.4.3 --with-gdb-version=6.6 --with-arch=armv5te --program-transform-name='s,^,arm-linux-androideabi-,'
  
  Thread model: posix
  
  gcc version 4.4.3 (GCC)    

  Goal is to utilize neon enabled ARM processor to boost x264 encoder performance...

• Is there a Heroku-supported method for getting the length of an audio file in seconds ?

  12 juillet 2013, par Ben West

  I'm trying to implement

  http://blog.firmhouse.com/validate-length-of-an-audio-file-when-using-paperclip-and-s3

  But I'm unsure what gem provided FFMpegWrapper, and I'd like to use Heroku to deploy my app for testing. Does heroku support something that will work for this ?

  full Rails Application source :

  https://github.com/mrgenixus/sound-byte

  Relevant Model :

  https://github.com/mrgenixus/sound-byte/blob/master/app/models/episode.rb

• ffmpeg settings or alternatives to ffmpeg on raspberry pi for video streaming

  14 octobre 2016, par andrei

  I have a Raspberry Pi (model B) running raspbian wheezy on a 16gb SD card. I also have a 32gb flash storage attached on the usb. I’m trying to stream a video (h264 encoded mp4 file 1280x720) over the ethernet from that flash storage.
  I’m using ffmpeg+ffserver. Here is ffserver.conf (relevant parts) :

  ...
  
  MaxBandwidth 10000
  
  <feed>
  
  ...
  
  FileMaxSize 100M
  
  ACL allow 127.0.0.1
  
  </feed>
  
  ...
  
  <stream>
  
  Feed feed1.ffm
  
  Format flv
  
  VideoSize 288x176 #made small just for testing
  
  NoAudio
  
  </stream>
  
  ....

  I start the ffserver, then call ffmpeg with this command :

  ffmpeg -re -an -i /mnt/u32/main.mp4 -r 25 -bit_rate 300k http://localhost:8090/feed1.ffm

  And I’m getting fps 3-5 at most. Naturally when I try to view the stream on another computer it’s very choppy and virtually unusable.

  Am I missing some settings ? Or perhaps there is another streaming solution that leverages the GPU instead of just the CPU as ffmpeg does ? I’m even open to suggestions about other boards (e.g. a pandaboard ? or clustering several RPi’s ?) Also, I’m flexible about the output format.