Recherche avancée

Sur d’autres sites (6334)

• ffmpeg xfade eating too much memory

  8 juin 2021, par Richard

  I am using ffmpeg to concatenate some clips with transitions, but I find the command is eating more than 10G memory in my virtual machine and it gets killed by the system.

  


  /var/log/messages as below :

  


  Jun  4 13:30:03 my-virtual-machine-1a2d66c92-10 kernel: Out of memory: Kill process 98880 (ffmpeg) score 862 or sacrifice child
Jun  4 13:30:03 my-virtual-machine-1a2d66c92-10 kernel: Killed process 98880 (ffmpeg) total-vm:23885828kB, anon-rss:15363036kB, file-rss:0kB, shmem-rss:0kB


  


  My ffmpeg command is as below :

  


  ffmpeg -i v0.mp4 -i v1.mp4 -i v2.mp4 -i v3.mp4 -i v4.mp4 -i v5.mp4 -i v6.mp4 -i v7.mp4 -i v8.mp4 -i v9.mp4 -i v10.mp4 -i v11.mp4 -i v12.mp4 -i v13.mp4 -i v14.mp4 -i v15.mp4 -i v16.mp4 -i v17.mp4 -filter_complex "[0:v][1:v]xfade=transition=fadeblack:duration=1.000:offset=8.960[v01];[v01][2:v]xfade=transition=fadeblack:duration=1.000:offset=16.120[v02];[v02][3:v]xfade=transition=fadeblack:duration=1.000:offset=25.760[v03];[v03][4:v]xfade=transition=fadeblack:duration=1.000:offset=35.400[v04];[v04][5:v]xfade=transition=fadeblack:duration=1.000:offset=43.640[v05];[v05][6:v]xfade=transition=fadeblack:duration=1.000:offset=51.880[v06];[v06][7:v]xfade=transition=fadeblack:duration=1.000:offset=64.680[v07];[v07][8:v]xfade=transition=fadeblack:duration=1.000:offset=80.320[v08];[v08][9:v]xfade=transition=fadeblack:duration=1.000:offset=88.720[v09];[v09][10:v]xfade=transition=fadeblack:duration=1.000:offset=98.320[v10];[v10][11:v]xfade=transition=fadeblack:duration=1.000:offset=107.920[v11];[v11][12:v]xfade=transition=fadeblack:duration=1.000:offset=112.840[v12];[v12][13:v]xfade=transition=fadeblack:duration=1.000:offset=141.560[v13];[v13][14:v]xfade=transition=fadeblack:duration=1.000:offset=149.560[v14];[v14][15:v]xfade=transition=fadeblack:duration=1.000:offset=154.880[v15];[v15][16:v]xfade=transition=fadeblack:duration=1.000:offset=160.080[v16];[v16][17:v]xfade=transition=fadeblack:duration=1.000:offset=165.160,format=yuv420p[video];[0:a][1:a]acrossfade=d=1.000:c1=tri:c2=tri[a01];[a01][2:a]acrossfade=d=1.000:c1=tri:c2=tri[a02];[a02][3:a]acrossfade=d=1.000:c1=tri:c2=tri[a03];[a03][4:a]acrossfade=d=1.000:c1=tri:c2=tri[a04];[a04][5:a]acrossfade=d=1.000:c1=tri:c2=tri[a05];[a05][6:a]acrossfade=d=1.000:c1=tri:c2=tri[a06];[a06][7:a]acrossfade=d=1.000:c1=tri:c2=tri[a07];[a07][8:a]acrossfade=d=1.000:c1=tri:c2=tri[a08];[a08][9:a]acrossfade=d=1.000:c1=tri:c2=tri[a09];[a09][10:a]acrossfade=d=1.000:c1=tri:c2=tri[a10];[a10][11:a]acrossfade=d=1.000:c1=tri:c2=tri[a11];[a11][12:a]acrossfade=d=1.000:c1=tri:c2=tri[a12];[a12][13:a]acrossfade=d=1.000:c1=tri:c2=tri[a13];[a13][14:a]acrossfade=d=1.000:c1=tri:c2=tri[a14];[a14][15:a]acrossfade=d=1.000:c1=tri:c2=tri[a15];[a15][16:a]acrossfade=d=1.000:c1=tri:c2=tri[a16];[a16][17:a]acrossfade=d=1.000:c1=tri:c2=tri[audio]" -map [video] -map [audio] -movflags +faststart test.mp4


  


  Is there a good way I can reduce or limit the memory that it uses ?

  


  Complete log at https://pastebin.com/AKAnbGGN

  


• Thread count option in FFmpeg for FASTEST conversion to h264 ?

  5 septembre 2013, par Saptarshi Biswas

  I need to maximize speed while converting videos using FFmpeg to h264

  • Any input format of source videos
  • User's machine can have any number of cores
  • Power and memory consumption are non-issues

  Of course, there are a whole bunch of options that can be tweaked but this question is particularly about choosing the best -thread <count></count> option. I am trying to find an ideal thread count as a function of

  • no. of cores
  • input video format
  • h264-friendly values maybe ?
  • anything else missed above ?

  I am aware the default -thread 0 follows one-thread-per-core approach which is supposed to be optimal. But I am not sure if this is time or space-optimized. Also, on certain testcases, I've seen more threads (say 4 threads on my dual core test machine) finishes quicker than the default.

  Any other direction, say configure options w.r.t. threads, worth pursuing ?

• Thread count option in FFmpeg for FASTEST conversion to h264 ?

  9 février, par S B

  I need to maximize speed while converting videos using FFmpeg to h264

  



  

  • Any input format of source videos

  


  • User's machine can have any number of cores

  


  • Power and memory consumption are non-issues

  


  



  Of course, there are a whole bunch of options that can be tweaked but this question is particularly about choosing the best -thread <count></count> option. I am trying to find an ideal thread count as a function of

  



  

  • no. of cores

  


  • input video format

  


  • h264-friendly values maybe ?

  


  • anything else missed above ?

  


  



  I am aware the default -thread 0 follows one-thread-per-core approach which is supposed to be optimal. But I am not sure if this is time or space-optimized. Also, on certain testcases, I've seen more threads (say 4 threads on my dual core test machine) finishes quicker than the default.

  



  Any other direction, say configure options w.r.t. threads, worth pursuing ?