Recherche avancée

Sur d’autres sites (6491)

• avutil : merge slice threading implementation from avcodec and avfilter

  11 juillet 2017, par Muhammad Faiz

  avutil : merge slice threading implementation from avcodec and avfilter
  Rework it to improve performance. Now mutex is not shared by workers,
  
  instead each worker has its own mutex and condition variable. This
  
  reduces lock contention between workers. Also use atomic variable for
  
  counter.
  The interface also allows execute to run special function on main
  
  thread, requested by Ronald.
  Signed-off-by : Muhammad Faiz <mfcc64@gmail.com>
  

  • [DH] libavutil/Makefile
  • [DH] libavutil/slicethread.c
  • [DH] libavutil/slicethread.h
  • [DH] libavutil/version.h

• Use popen with a relative or absolute path on Windows in C

  9 juillet 2017, par Tiwenty

  I’m trying to a GUI wrapper for FFmpeg. I decided to build my program around the binary instead of the libraries. I want to call ffmpeg.exe in parallel to my program and get the console output instantly to parse it and show to the user a progress bar or something.

  So I found popen which sends me the output when it comes so I can do what I want with it. But there are some problems with paths in popen on Windows.

  When I try ffmpeg.exe -i TEST.mkv TEST.mp4 (when I’m in the folder of both ffmpeg.exe and my source file either from start or a chdir) it works well and I get what I want.

  But when I do

  bin/ffmpeg.exe -i TEST.mkv TEST.mp4

  (with the executable obviously being in the bin folder) it doesn’t find the command bin :

  'bin' is not recognized as an internal or external command, operable program or batch file.

  It also doesn’t work with quotation marks around the path :

  "bin/ffmpeg.exe" -i TEST.mkv TEST.mp4

  But it does work with an absolute path and quotation marks :

  "C:/PATH/TO/USER/FFmpeg GUI/bin/ffmpeg.exe" -i jellyfish.mkv jellyfish.mp4.

  But it gets funnier.

  If I use relative paths for the source and output, it works.

  "C:/Users/tibtw_000/Raccourci/Code/FFmpeg GUI/bin/ffmpeg.exe" -i videos/jellyfish.mkv videos/jellyfish.mp4

  But if I want to put an absolute path to my source or output files, it now doesn’t work.

  "C:/PATH/TO/USER/FFmpeg GUI/bin/ffmpeg.exe" -i "C:/PATH/TO/USER/FFmpeg GUI/videos/jellyfish.mkv"

  and now returns

  'C:/PATH/TO/USER/FFmpeg' is not recognized as an internal or external command, operable program or batch file.

  Now I’m starting to wonder if the space in my path is at fault. And it was. When I use

  C:/PATH/TO/USER/FFmpegGUI/bin/ffmpeg.exe -i C:/PATH/TO/USER/FFmpegGUI/videos/jellyfish.mkv C:/PATH/TO/USER/FFmpegGUI/videos/jellyfish.mp4 in popen everything works perfectly.

  So what should I do ? Do I force the user to not put his files in paths with spaces ? Is there a special character that I can put instead of a normal space in the path to make popen understand what I want it to do ?

• Correcting the variable name in an ffmpeg subtitle script

  21 juin 2017, par Steven Foong

  I have 175 mp4 video files and subtitle files with the extension .ass. Unfortunately, my smart TV is not able to read those subtitles. I plan to burn (hardcode) the subtitles into the video.

  I use this command :

  ffmpeg -i orgvideo.mp4 -vf subtitles="subtitle.ass" newvideo.mp4     <br />

  It works. So I plan to use a bash script to automate the process.

  Everything in the script is working but the ffmpeg command line isn’t able to retrieve the subtitle variable.

  After googling around, I found that my file name has special character and space, that causes my script to fail. If the video file name and the subtitle file is simple, then the script should be no problem.

  This is my script :

  for f in *.mp4
  
  do
  
      new="${f%%.mp4} (CHT).mp4"
  
      subtitle="${f%%.mp4}.chi.ass"
  
      < /dev/null ffmpeg -i "$f" -vf subtitles="$subtitle" "$new"
  
  done

  The ffmpeg line is having problems reading the subtitle file variable. Can anyone help ?