Recherche avancée

Sur d’autres sites (9996)

• avformat/matroskadec : Improve invalid length error handling

  17 mai 2019, par Andreas Rheinhardt

  avformat/matroskadec : Improve invalid length error handling
  1. Up until now, the error message for EBML numbers whose length exceeds
  
  the limits imposed upon them because of the element's type did not
  
  distinguish between known-length and unknown-length elements. As a
  
  consequence, the numerical value of the define constant
  
  EBML_UNKNOWN_LENGTH was emitted as part of the error message which is
  
  of course not appropriate. This commit changes this by adding error
  
  messages designed for unknown-length elements.
  2. We impose some (arbitrary) sanity checks on the lengths of certain
  
  element types ; these checks were conducted before the checks depending
  
  on whether the element exceeds its containing master element. Now the
  
  order has been reversed, because a failure at the (formerly) latter
  
  check implies that the file is truly erroneous and not only fails our
  
  arbitrary length limit. Moreover, this increases the informativeness of
  
  the error messages.
  3. Furthermore, the error message in general has been changed by replacing
  
  the type of the element (something internal to this demuxer and
  
  therefore suitable as debug output at best, not as an error message
  
  intended for ordinary users) with the element ID. The element's position
  
  has been added, too.
  4. Finally, the length limit for EBML_NONE elements has been changed so
  
  that all unknown-length elements of EBML_NONE-type trigger an error.
  
  This is done because unknown-length elements can't be skipped and need
  
  to be parsed, but there is no syntax to parse available for EBML_NONE
  
  elements. This is done in preparation for a further patch which allows
  
  more unknown-length elements than just clusters and segments.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavformat/matroskadec.c

• lavu/opt : fix range check logic in set_format()

  16 décembre 2013, par Stefano Sabatini

  lavu/opt : fix range check logic in set_format()
  In particular, allow to reject undefined values. Previously the code
  
  was only accepting values in the range -1 .. NB_FORMATS-1.
  

  • [DH] libavutil/opt.c

• Extract part of a video using ffmpeg_extract_subclip - black frames

  20 août 2020, par albert1905

  I'm trying to use : "ffmpeg_extract_subclip" for extracting part of a video.

  


  And I'm facing a few problems :

  


  1.when I'm cutting a small video (1-3seconds) I'm getting black frames, only audio is working.
2.when I'm cutting longer video, the output video is stuck 2-3 seconds before the end.

  


  This is my simple code :

  


  from moviepy.video.io.ffmpeg_tools import ffmpeg_extract_subclip

input_video_path = 'myPath/vid1.mp4'
output_video_path = 'myPath/output/vid1.mp4'
t1 = 6.5
t2 = 16    # random numbers, my last attempt..
    
ffmpeg_extract_subclip(input_video_path, t1, t2, targetname=output_video_path)


  


  I tried to look inside the code :
ffmpeg_extract_subclip Function

  


  But still couldn't understand what's wrong.. :(

  


  I'm still trying, and if anyone knows the problem or have a different approach, that will be amazing.

  


  Thanks a lot for your help !