Recherche avancée

Sur d’autres sites (11997)

• How convert High bitrate mp3 to lower rate using ffmpeg in android

  31 mars 2017, par Android Weblineindia

  We want to convert 320kbps mp3 file to 128kbps mp3 so currently we are using below ffmpeg command but its not working.

  ffmpeg -i input.mp3 -codec:a libmp3lame -qscale:a 5 output.mp3

  Result :-the output bitrate same as input mp3.

  And we are following the FFmpeg Encoding guideline for that here is the link :- https://trac.ffmpeg.org/wiki/Encode/MP3

  so please suggest any solution.

• doc : delete viterbi.txt

  10 novembre 2013, par Timothy Gu

  doc : delete viterbi.txt
  The description has been moved to the FFmpeg wiki :
  
  https://trac.ffmpeg.org/wiki/ViterbiAlgorithm
  Signed-off-by : Timothy Gu <timothygu99@gmail.com>
  

  • [DH] doc/viterbi.txt

• 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 ?