Sur d’autres sites (7937)

• libavcodec/alpha : remove DSP & support code

  9 juin 2024, par Sean McGovern

  libavcodec/alpha : remove DSP & support code
  Introduced in 1992, the Alpha was a 64-bit RISC processor designed
  
  to replace the VAX CISC machines sold by Digital Equipment Corporation.
  After Digital was acquired by Compaq in 1998 — who themselves would be
  
  later purchased by Hewlett-Packard, the architecture was phased out over
  
  the following decade. It became effectively defunct in 2007, the last
  
  publicly available processor being the Alpha 21364.
  FFmpeg has not added any DSP code for this architecture since lowres2
  
  was introduced in 2012, and it is more than unlikely someone still wishes
  
  to maintain it.
  Remove the DSP and support code.
  Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>
  

  • [DH] Changelog
  • [DH] configure
  • [DH] libavcodec/alpha/Makefile
  • [DH] libavcodec/alpha/asm.h
  • [DH] libavcodec/alpha/blockdsp_alpha.c
  • [DH] libavcodec/alpha/hpeldsp_alpha.c
  • [DH] libavcodec/alpha/hpeldsp_alpha.h
  • [DH] libavcodec/alpha/hpeldsp_alpha_asm.S
  • [DH] libavcodec/alpha/idctdsp_alpha.c
  • [DH] libavcodec/alpha/idctdsp_alpha.h
  • [DH] libavcodec/alpha/idctdsp_alpha_asm.S
  • [DH] libavcodec/alpha/me_cmp_alpha.c
  • [DH] libavcodec/alpha/me_cmp_mvi_asm.S
  • [DH] libavcodec/alpha/mpegvideo_alpha.c
  • [DH] libavcodec/alpha/pixblockdsp_alpha.c
  • [DH] libavcodec/alpha/regdef.h
  • [DH] libavcodec/alpha/simple_idct_alpha.c
  • [DH] libavcodec/blockdsp.c
  • [DH] libavcodec/hpeldsp.c
  • [DH] libavcodec/idctdsp.c
  • [DH] libavcodec/me_cmp.c
  • [DH] libavcodec/mpegvideo.c
  • [DH] libavcodec/pixblockdsp.c

• ffmpeg drops the moov atom when coverting mp4 to ogg, flv, or webm

  31 janvier 2014, par user1370897

  I'm using processor qtfaststart and the gem paperclip-ffmpeg in Rails to convert an mp4 file to either ogg, webm, or flv. However, I haven't had any success converting the mp4 file to these formats for streaming purposes because the moov atom gets dropped (converting mp4 to mp4 keeps its moov atom though*).

  I did a $ qtfaststart -l on the original mp4 file and I get this :

  ftyp (24 bytes)
  
  moov (5691 bytes)
  
  free (399309 bytes)
  
  mdat (12312760 bytes)

  Which shows me that the mp4 file has an moov atom in there. The command that paperclip-ffmpeg is executing is something like this :

  $ ffmpeg -i ~/Movies/VID_20140119_134445.mp4 -acodec libvorbis -ac 2 -ab 96k -ar 44100 -s 640x360 -y ~/tmp/iguana.webm

  However, doing a qtfaststart on the new file (iguana.webm) I get the following :

  $ qtfaststart -l ~/tmp/iguana.webm 
  
  moov atom not found, is this a valid MOV/MP4 file?
  
  Traceback (most recent call last):
  
  File "/usr/local/bin/qtfaststart", line 5, in <module>
  
  pkg_resources.run_script(&#39;qtfaststart==1.8&#39;, &#39;qtfaststart&#39;)
  
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 489, in run_script
  
  self.require(requires)[0].run_script(script_name, ns)
  
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/pkg_resources.py", line 1214, in run_script
  
  exec script_code in namespace, namespace
  
  File "/Library/Python/2.7/site-packages/qtfaststart-1.8-py2.7.egg/EGG-INFO/scripts/qtfaststart", line 17, in <module>
  
  
  
  File "build/bdist.macosx-10.9-intel/egg/qtfaststart/command.py", line 44, in run
  
  File "build/bdist.macosx-10.9-intel/egg/qtfaststart/processor.py", line 65, in get_index
  
  File "build/bdist.macosx-10.9-intel/egg/qtfaststart/processor.py", line 106, in _ensure_valid_index
  
  qtfaststart.exceptions.FastStartException
  
  </module></module>

  I've also tried adding the option -movflags faststart to the command ffmpeg but ffmpeg still keeps dropping the moov atom to the output file.

  I'm using Rails 4, paperclip-ffmpeg 1.0.1, ffmpeg 2.1.3 Built on Jan 28 2014. Any help would be greatly appreciated.

• ffmpeg commands not working in micromax android

  10 février 2014, par pavan

  I am able to execute ffmpeg commands on android devices like Samsung,LG and Sony but in Micromax it's not working. I have built ffmpeg library for arm processor. I could not collect the log because I am not able to connect the device. I have following questions on this,
  1) Why it's not working on Micromax ?
  2) I do not want to show my app on other device apart from ARM based android device, is it possible to control ?

  The below configuration I have used while building ffmpeg,

   !/bin/bash

  cd ffmpeg

  export TMPDIR=tmp
  mkdir -p $TMPDIR

  Android NDK Location

  NDK=/Users/sunitha/Downloads/android-ndk-r9c

  ANDROID_API=android-9
  SYSROOT=$NDK/platforms/$ANDROID_API/arch-arm
  PREBUILT=$NDK/toolchains/arm-linux-androideabi-4.6/prebuilt/darwin-x86
  CROSS_PREFIX=$PREBUILT/bin/arm-linux-androideabi-
  ARM_INCLUDE=$SYSROOT/usr/include
  ARM_LIB=$SYSROOT/usr/lib
  PREFIX=../build
  OPTIMIZE_CFLAGS=" -marm -march=armv6 "
  ADDITIONAL_CONFIGURE_FLAG=

  Location of lame's static installation

  MP3LAME=../libmp3lame
  X264=../libx264

  ./configure \
  —arch=arm \
  —target-os=linux \
  —enable-cross-compile \
  —cross-prefix=$CROSS_PREFIX \
  —prefix=$PREFIX \
  —sysroot=$SYSROOT \
  —extra-cflags=" -I$ARM_INCLUDE -I$MP3LAME/include -I$X264/include -DANDROID $OPTIMIZE_CFLAGS" \
  —extra-ldflags=" -L$ARM_LIB -L$MP3LAME/lib -L$X264/lib" \
  —disable-debug \
  —enable-libmp3lame \
  —enable-libx264 \
  —disable-ffplay \
  —disable-ffprobe \
  —disable-ffserver \
  —enable-avfilter \
  —enable-decoders \
  —enable-demuxers \
  —enable-encoders \
  —enable-filters \
  —enable-indevs \
  —enable-network \
  —enable-parsers \
  —enable-protocols \
  —enable-swscale \
  —enable-gpl \
  —enable-nonfree \
  $ADDITIONAL_CONFIGURE_FLAG

  cd ..