Recherche avancée

Sur d’autres sites (15641)

• FFmpeg library does not want to images into video

  27 avril 2021, par ArtisticBytes

  I am trying to create image folder with 600 images with file names : animation_010000.jpg to animation_010600.jpg (so animation_010000.jpg, animation_010001.jpg, animation_010002.jpg, and all the way to animation_010600.jpg) into a video file, but somehow FFmpeg does not see the path right. What I am doing wrong ?
I tried 4 different samples still the same error in the input path.

  


  ffmpeg -r 60  -s 1920x1080 -i "animation_010%03d.jpg" -vcodec libx264 -crf 25  -pix_fmt yuv420p "test.mp4"


  


  or

  


  ffmpeg -r 60  -s 1920x1080 -i "animation_010%3d.jpg" -vcodec libx264 -crf 25  -pix_fmt yuv420p "test.mp4"


  


  or

  


  ffmpeg -r 60  -s 1920x1080 -i "animation_%06d.jpg" -vcodec libx264 -crf 25  -pix_fmt yuv420p "test.mp4"


  


  or

  


  ffmpeg -r 60  -s 1920x1080 -i "animation_%6d.jpg" -vcodec libx264 -crf 25  -pix_fmt yuv420p "test.mp4"


  


  Keep in mind that input path of the folder is F:/AnimationImages/ but I am not using the full path address instead of I installed all the FFmpeg library into the folder with the images. Also, keep in mind that it converts a single image file as input into a video file as output without any errors. I am pretty sure that answer in input path formatting - so what I am doing wrong ? My OS is Windows 10 and I am using cmd.exe with administrator rights. Thanks guys.

  


• x86inc : Clear __SECT__

  26 mai 2015, par Timothy Gu

  x86inc : Clear __SECT__
  This commit silences warning(s) like :
      libavcodec/x86/fft.asm:93 : warning : section flags ignored on section
  
      redeclaration
  The cause of this warning is that because `struc` and `endstruc` attempts to
  
  revert to the previous section state [1]. The section state is stored in the
  
  macro __SECT__, defined by x86inc.asm to be `.note.GNU-stack ...`, through the
  
  `SECTION` directive [2].  Thus, the `.note.GNU-stack` section is defined twice
  
  (once in x86inc.asm, once during `endstruc`), causing the warning.
  That is the first part of the commit : using the primitive `[section]` format
  
  for .note.GNU-stack etc., which does not update `__SECT__` [2].
  That fixes only half of the problem. Even without any `SECTION` directives,
  
  `__SECT__` is predefined as `.text`, which conflicting with the later
  
  `SECTION_TEXT` (which expands to `.text align=16`).
  [1] : http://www.nasm.us/doc/nasmdoc6.html#section-6.4
  
  [2] : http://www.nasm.us/doc/nasmdoc6.html#section-6.3
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavutil/x86/x86inc.asm

• Encoded images into H264 video are skipped and/or missing ?

  25 juillet 2013, par Jona

  I'm trying to encode images into an H264 MP4 video. The issues I'm having is that some of the images are skipped or at the end of the video simply missing. I need the video to play every single image I encode since it is an animation.

  Any help setting the encoder properly would be greatly appreciated !

  Encoder settings :

  AVCodecContext *c;
  
  ...
  
  c->codec_id = AV_CODEC_ID_H264;
  
  c->bit_rate = mOutputWidth*mOutputHeight*4;//400000;
  
  /* Resolution must be a multiple of two. */
  
  c->width    = mOutputWidth;
  
  c->height   = mOutputHeight;
  
      /* timebase: This is the fundamental unit of time (in seconds) in terms
  
       * of which frame timestamps are represented. For fixed-fps content,
  
       * timebase should be 1/framerate and timestamp increments should be
  
       * identical to 1. */
  
  c->time_base.den = mFps;
  
  c->time_base.num = 1;
  
  c->gop_size      = 12; /* emit one intra frame every twelve frames at most */
  
  c->pix_fmt       = AV_PIX_FMT_YUV420P;
  
  ...
  
  av_dict_set(&pOptions, "preset", "medium", 0);
  
  av_dict_set(&pOptions, "tune", "animation", 0);
  
  
  
  /* open the codec */
  
  ret = avcodec_open2(c, codec, &pOptions);
  
  if (ret < 0) {
  
      LOGE("Could not open video codec: %s", av_err2str(ret));
  
      return -1;
  
  }

  Update 07/24/13 :
  I was able to achieve a better video by setting the gop_size=FPS and writing the last video frame repeatedly FPS+1 times seemed to resolve all issues. To me it seems odd to do that but might be something standard in the video encoding world ? Any tips feedback about this ?