Recherche avancée

Sur d’autres sites (5330)

• Where I made a mistake - FFmpeg (Linux) basic problem

  23 mars 2019, par Fejor

  I just started learning FFmpeg. I have code (like below), but it’s doing nothing.

  fmpeg -i videoplayback.mp4 -filter_complex "[1:v]trim=start=0:end=1,setpts=PTS-STARTPTS,scale=480x360,setsar=sar=16/9[intro1];
  
  [1:v]trim=start=1:end=123.39,setpts=PTS-STARTPTS,scale=480x360,setsar=sar=16/9[main1];
  
  [1:v]trim=start=123.39:end=124.39,setpts=PTS-STARTPTS,scale=480x360,setsar=sar=16/9[end1];
  
  [intro1]format=pix_fmts=yuva420p, fade=t=in:st=0:d=1:alpha=1[intro1];
  
  [end1]format=pix_fmts=yuva420p, fade=t=in:st=0:d=1:alpha=1[end1];
  
  [intro1][main1][end1][output];
  
  [a:1][audio]; -vcodec libx264 -map "[output]" -map"[audio]" "output.mp4"

• Which is the better way to use ffmpeg ?

  11 mai 2016, par seaguest

  We need ffmpeg to do some video processing, like video format conversion, live stream snapshot..., we won’t go deep in ffmpeg.

  Now I am wondering what would be the better way to use ffmpeg, we are developping in Golang, either we call ffmpeg like shell command line, or we use libav* library of ffmpeg.

  command line:
  
      Pros: 
  
          easy to use, reliable (I got a quality loss problem with library mode), many tutorials
  
      Cons:
  
          the is is a separate process, out of our control, we can't get detailed information of the process, like the video conversion progressing data
  
          the command line way seems not so cool, this is not well integrated in the whole project.
  
  
  
  libav* library:
  
      Pros:
  
          we can have the process detailed data, progressing status....
  
          ...
  
  
  
      Cons:
  
          difficult to use, much less materials

  Could anyone give your idea which is the better way to use ffmpeg ?

  Before this question, I have asked another two questions :

  One is regarding calling libav* library caused the qulity loss problem :
  Why calling libav* library doesn’t have same quality as ffmpeg command line ?

  One is for command line progressing status retrieving problem :
  How to get the realtime output for a shell command in golang ?

• FATE/dnn : let fate/dnn tests depend on ffmpeg static libraries

  7 août 2019, par Guo, Yejun

  FATE/dnn : let fate/dnn tests depend on ffmpeg static libraries
  background :
  
  DNN (deep neural network) is a sub module of libavfilter, and FATE/dnn
  
  is unit test for the DNN module, one unit test for one dnn layer.
  
  The unit tests are not based on the APIs exported by libavfilter,
  
  they just directly call into the functions within DNN submodule.
  There is an issue when run the following command :
  
  build$ ../ffmpeg/configure —disable-static —enable-shared
  
  make
  
  make fate-dnn-layer-pad
  And part of error message :
  
  tests/dnn/dnn-layer-pad-test.o : In function `test_with_mode_symmetric' :
  
  /work/media/ffmpeg/build/src/tests/dnn/dnn-layer-pad-test.c:73 : undefined reference to `dnn_execute_layer_pad'
  The root cause is that function dnn_execute_layer_pad is a LOCAL symbol
  
  in libavfilter.so, and so the linker could not find it when build dnn-layer-pad-test.
  
  To check it, just run : readelf -s libavfilter/libavfilter.so | grep dnn
  So, add dependency in fate/dnn Makefile with ffmpeg static libraries.
  
  This is the same method used in fate/checkasm
  Signed-off-by : Guo, Yejun <yejun.guo@intel.com>
  
  Signed-off-by : Pedro Arthur <bygrandao@gmail.com>
  

  • [DH] tests/dnn/Makefile