Recherche avancée

Sur d’autres sites (9173)

• FFMPEG concat cutting audio off after certain clip

  10 avril 2020, par legit_hacker_2000

  So I am creating multiple video clips in Python using FFMPEG, I am then trying to concat these together. I create multiple videos named result1000, result1001 etc, then I create a transition effect I want to layer between these videos. The result1000, result1001... etc concat together perfectly fine, however inserting the transition effect between them causes every clip after the first transition to lose audio.

  



  Creating the transiton

  



  ffmpeg -loop 1 -y -i media/templates/bg.png -i media/swoosh_sound.mp3 -shortest -acodec copy -vcodec libx264rgb output/swoosh.mp4


  



  Creating video clips

  



  ffmpeg -loop1 -y -i image_files/image+str(1000+i)+.png -i audio_files/audio+str(1000+i)+.mp3 -shortest -acodec copy -vcodec libx264rgb output/result+str(1000+i)+.mp4


  



  The ffmpeg_files.txt then looks something like this

  



  file 'output/result1000.mp4'
file 'output/result1001.mp4'
file 'output/result1002.mp4'
file 'output/result1003.mp4'
file 'output/result1004.mp4'
file 'output/swoosh.mp4'
file 'output/result1005.mp4'
file 'output/result1006.mp4'


  



  and the concat command im using is

  



  ffmpeg -f concat -safe 0 -i ffmpeg_files.txt output/no_bg_out.mp4


  



  In console on running the concat comment it will say

  



  [mov,mp4,m4a,3gp,3g2,mj2 @ 000001f289b44c40] Auto-inserting h264_mp4toannexb bitstream filter


  



  for each resultXXXX clip, then as soon as it reaches a transition clip it starts spamming

  



  [mp4 @ 000001aa093ad100] Non-monotonous DTS in output stream 0:1; previous: 13619623, current: 8777816; changing to 13619624. This may result in incorrect timestamps in the output file.


  



  I have read over the solutions mentioned Here but none of them seem to solve my issue. It should be noted that all video clips are created from .mp3 audio files and .png image files.

  


• avcodec/adpcm : Clip step index for ADPCM_IMA_APM

  1er mars 2020, par Michael Niedermayer

  avcodec/adpcm : Clip step index for ADPCM_IMA_APM
  Fixes : out of array access
  
  Fixes : 20828/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_ADPCM_IMA_APM_fuzzer-5712770106654720
  Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
  
  Reviewed-by : Paul B Mahol <onemda@gmail.com>
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/adpcm.c

• Concatenating video clip with static image causes buffer errors

  16 février 2020, par jgaeb

  I’m trying to concatenate a 15 second clip of a video (MOVIE.mp4) with 5 seconds (no audio) of an image (IMAGE.jpg) using FFmpeg.

  Something seems to be wrong with my filtergraph, although I’m unable to determine what. The command I’ve put together is the following :

  ffmpeg \
  
  -loop 1 -t 5 -I IMAGE.jpg \
  
  -t 15 -I MOVIE.mp4 \
  
  -filter_complex "[0:v]scale=480:640[1_v];anullsrc[1_a];[1:v][1:a][1_v][1_a]concat=n=2:v=1:a=1[out]" \
  
  -map "[out]" \
  
  -strict experimental tst_full.mp4

  Unfortunately, this seems to be creating some strange results :

  1. On my personal computer (FFmpeg 4.2.1) it correctly concatenates the movie with the static image ; however, the static image lasts for an unbounded length of time. (After entering ctrl-C, the movie is still viewable, but is of an extremely long length—e.g., 35 min—depending on when I interrupt the process.)

  2. On a remote machine where I need to do the ultimate video processing (FFmpeg 2.8.15-0ubuntu0.16.04.1), the command does not terminate, and instead, I get cascading errors of the following form :

  Past duration 0.611458 too large
  
  ...
  
  [output stream 0:0 @ 0x21135a0] 100 buffers queued in output stream 0:0, something may be wrong.
  
  ...
  
  [output stream 0:0 @ 0x21135a0] 100000 buffers queued in output stream 0:0, something may be wrong.

  I haven’t been able to find much documentation that elucidates what these errors mean, so I don’t know what’s going wrong.