Recherche avancée

Sur d’autres sites (5365)

• Is it possible to determine if a subtitle track is imaged based or text based with ffprobe

  21 février 2021, par Shex

  I'm writing a script that burns subtitles into video files to prepare them for a personal stream I'm hosting. I'm having a hard time finding which type of subtitle is used in the file. I use ffprobe to get the files' information, and I can get stuff like the codec type, but I was wondering if there is a way to determine if a subtitle track is image based or text based. I can only think of getting a list of all possible codecs and match the codec type with this list but it would be very useful to have an info somewhere that can tell me "OK this is an image-based subtitle track", as when I burn I cannot use the same filters with ffmpeg to burn image vs. text subtitles.

  


• libavfilter/dnn : determine dnn output during execute_model instead of set_input_output

  25 avril 2019, par Guo, Yejun

  libavfilter/dnn : determine dnn output during execute_model instead of set_input_output
  Currently, within interface set_input_output, the dims/memory of the tensorflow
  
  dnn model output is determined by executing the model with zero input,
  
  actually, the output dims might vary with different input data for networks
  
  such as object detection models faster-rcnn, ssd and yolo.
  This patch moves the logic from set_input_output to execute_model which
  
  is suitable for all the cases. Since interface changed, and so dnn_backend_native
  
  also changes.
  In vf_sr.c, it knows it's srcnn or espcn by executing the model with zero input,
  
  so execute_model has to be called in function config_props
  Signed-off-by : Guo, Yejun <yejun.guo@intel.com>
  
  Signed-off-by : Pedro Arthur <bygrandao@gmail.com>
  

  • [DH] libavfilter/dnn_backend_native.c
  • [DH] libavfilter/dnn_backend_native.h
  • [DH] libavfilter/dnn_backend_tf.c
  • [DH] libavfilter/dnn_backend_tf.h
  • [DH] libavfilter/dnn_interface.h
  • [DH] libavfilter/vf_sr.c

• ffmpeg trim mp3 - determine precisely the start and end times of section to be trimmed

  4 février 2019, par Ahmed Khalil

  I have a long mp3 track of an audio book (more than 9 hours long) that I would like to trim using ffmpeg.

  The sample code below is used to trim an mp3 section by providing the start and end times. However, when I determine the start and end times, then checking the output file, it’s not as precisely as I want, sometimes several minutes ahead/before the desired point.

  import subprocess
  
  file = r'audio book.mp3'
  
  track_name = "trimmed section"
  
  output = r'D:\{0}'.format(track_name)
  
  start = '01:26:04'
  
  end = '01:33:17'
  
  
  
  d = subprocess.getoutput('ffmpeg -i "{0}" -ss {1} -to {2} -c copy {3}.mp3"'
  
                       .format(file, start, end, output))
  
  
  
  print(d)

  Is there a way to determine with accuracy the real start and end time of an mp3 audio track, to be given afterwards as inputs to the code...to trim the desired sections all at once, without the need to adjust/fine-tune the start and end time manually ??