Recherche avancée

Sur d’autres sites (7277)

• Problems compiling ffmpeg for iOS

  19 août 2012, par marchinram

  I seen a few posts similar to this one but the problem I'm having is slightly different, I downloaded the ffmpeg source and ran configure like below :

  ./configure --disable-doc --disable-ffmpeg --disable-ffplay --disable-ffserver \ 
  
  --enable-cross-compile --arch=arm --target-os=darwin \ 
  
  --cc=/applications/xcode.app/contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/gcc --as='gas-preprocessor/gas-preprocessor.pl /applications/xcode.app/contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/gcc' \ 
  
  --sysroot=/applications/xcode.app/contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.1.sdk \ 
  
  --cpu=cortex-a8 --extra-cflags='-arch armv7' --extra-ldflags='-arch armv7 \ 
  
  -isysroot /applications/xcode.app/contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS5.1.sdk' --enable-pic

  The configure appears to work right, it ends with this

  License: LGPL version 2.1 or later
  
  Creating config.mak and config.h...
  
  
  
  WARNING: Compiler does not indicate floating-point ABI, guessing soft.

  But when I then run make I get this

  AS  libavcodec/arm/ac3dsp_armv6.o
  
  ./libavutil/arm/asm.S:178:garbage following instruction -- `ldr r4,.Lpicoff\'
  
  ./libavutil/arm/asm.S:179:Unknown pseudo-op: .Lpic
  
  ./libavutil/arm/asm.S:179:Rest of line ignored. 1st junk character valued 92 (\).
  
  ./libavutil/arm/asm.S:181:Unknown pseudo-op: .altmacro
  
  ./libavutil/arm/asm.S:182:Unknown pseudo-op: .noaltmacro
  
  ./libavutil/arm/asm.S:185:Unknown pseudo-op: .Lpic
  
  ./libavutil/arm/asm.S:185:Rest of line ignored. 1st junk character valued 92 (\).
  
  ./libavutil/arm/asm.S:178:garbage following instruction -- `ldr lr,.Lpicoff\'
  
  ./libavutil/arm/asm.S:179:Unknown pseudo-op: .Lpic
  
  ./libavutil/arm/asm.S:179:Rest of line ignored. 1st junk character valued 92 (\).
  
  ./libavutil/arm/asm.S:181:Unknown pseudo-op: .altmacro
  
  ./libavutil/arm/asm.S:182:Unknown pseudo-op: .noaltmacro
  
  ./libavutil/arm/asm.S:185:Unknown pseudo-op: .Lpic
  
  ./libavutil/arm/asm.S:185:Rest of line ignored. 1st junk character valued 92 (\).
  
  make: *** [libavcodec/arm/ac3dsp_armv6.o] Error 1

  Any help would be greatly appreciated

• How to save ffmpeg segmets to disk immediately with sub-second intervals ?

  20 octobre 2023, par amfast

  I'm trying to record video on a raspberry and have it save as much as possible (sub-second resolution) in case of a power cutoff.

  


  I use -f segment to save the encoded stream in 100ms segments with the hope that all but the interrupted (by power cutoff) segment will be saved in memory. Unfortunately, when cutting off power, all the destination files (output_0001.mp4, output_0002.mp4, ...) are created, but empty.

  


  To save the files to disk immediately, I added the -strftime 1 option that allows formatting the output filename as time. It seems weird that this is the (only ?) way to trigger immediate saving of files, but it works - untill I try to have segments smaller than 1 second. The problem seems to be that the format string %d, that previously added a sequence number in my output filenames, now represents "day" (i.e. date) and the smallest resolution time format string is %S for second. I saw %f suggested somewhere for smaller resolutions, but it only prints "%f".

  


  The result is that the segmentation part of ffmpeg does create 100ms segments and save them to disk immediately, but the strftime feature gives the output files names that only change every second, so all the interim files are overwritten.

  


  Example of the failing command below. Without the -strftime option this creates nice segments, but does not save them to disk immediately.

  


  libcamera-vid --flush \
    --framerate ${FRAMERATE} \
    --width ${WIDTH} \
    --height ${HEIGHT} \
    -n \
    -t ${TIMEOUT} \
    --codec yuv420 \
    -o - | 
ffmpeg \
    -fflags nobuffer \
    -strict experimental \
    -loglevel debug \
    -flags low_delay \
    -f rawvideo \
    -pix_fmt yuv420p \
    -s:v ${WIDTH}x${HEIGHT} \
    -r ${FRAMERATE} \
    -i - \
    -c:v h264_v4l2m2m \
    -f segment \
    -segment_time 0.1 \
    -segment_format mp4 \
    -reset_timestamps 1 \
    -strftime 1 \
    -b:v ${ENCODING_BITRATE} \
    -g 1 \
    "output_%04d.mp4"


  


  Question :
  
Is there another way besides -strftime to trigger immediate saving ? Or is there a mechanism to feed finer resolution format strings to the output filename ?

  


• Anomalie #3219 : Chaine de langue dans affdate_debut_fin

  19 juillet 2014, par cam.lafit -

  Bonjour

  Oui il est possible de proposer un PR depuis github.
  Il est aussi possible d’exploiter les fonctionnalités de patch fournit
  par git (à poser dans le ticket ou envoi par mail)