Recherche avancée

Sur d’autres sites (6705)

• Displaying ffmpeg conversion progress

  29 mars 2014, par Hiigaran

  I'm trying to get an admin function made, in which I want to show a basic status of any file conversion(s) that may or may not be happening upon page load. I'm not entirely sure how to proceed with this, so here is what I have at the moment :

  exec("ffprobe -v quiet -print_format json -show_format '".$fileNameIn.".".$ext."' > /var/www/resources/ffmpegFormat.log");
  
  exec("/ffmpeg/ffmpeg -loglevel 'verbose' -i '".$fileNameIn.".".$ext."' '".$fileNameOut.".flac' null >/dev/null 2>/var/www/resources/ffmpeg.log &",$ffmpegOutput);

  My idea is to use ffprobe to output some information about the file to be converted, then use PHP in some way to read the output file (ffmpegFormat.log) for the total file duration. Once read, ffmpeg begins, while outputting to its own file (ffmpeg.log).

  I'm not looking for anything fancy, like live updates on the progress, so I'm content with simply having a script read the current duration from the last line of the ffmpeg.log file, compare it to the total duration from the ffmpegFormat.log file, and display a percentage only after a page load/refresh.

  I've placed a restriction on conversion to only one file at a time, for the sake of simplifying this progress indicator (and due to a lack of processing power on this computer).

  Assuming there's no simpler way than my idea, how can I do this ?

• avcodec/speexdec : Consider mode in frame size check

  26 décembre 2021, par Michael Niedermayer

  avcodec/speexdec : Consider mode in frame size check
  No speex samples with non default frame sizes are known (to me)
  
  the official speexenc seems to only generate the 3 default ones.
  
  Thus it may be that the fuzzer samples where the first non default
  
  values encountered by the decoder.
  
  Possibly the "<" should be " !="
  Fixes : out of array access
  
  Fixes : 42821/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_SPEEX_fuzzer-5640695772217344
  Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/speexdec.c

• three ways to achieve an H264 file

  18 mars 2016, par Kindermann

  here I have three ways to get an H264 file, like all forensic scientists, I am very curious about the differences between them :

  1.

  ffmpeg -i video.mp4 video.h264

  2.

  ffmpeg -i video.mp4 -vcodec copy -an -f h264 video.h264

  3. Using the example "demuxing_decoding.c" provided on the ffmpeg official website :
  http://ffmpeg.org/doxygen/trunk/demuxing_decoding_8c-example.html

  Obviously, the first one does the transformation, and the second one does the demuxing. They render different H264 files which however have similar file sizes(in my case, it’s about say 24 MB). Suprisingly, the third one, which is also supposed to do the demuxing job, renders an H264 file with 8.4 GB ! Why ?

  What I wondered is really, how the interiors of these three methods work ?(The third one is already in source code, therefore it’s quite easy to have an insight) What about the first two commands ? What APIs are called when executing these two commands and how those APIs are called(namely, in what kind of sequences they are called) and things like that.
  One thing that is also important to me is, i have no idea how I can trace the execution routines of ffmpeg command lines. I want to see what’s going on behind ffmpeg commands in source code version. Is it possible ?

  I appreciate any comment.