Le septidi 27 frimaire, an CCXXIV, Ned Rockson a écrit : > > > Of course -- I'm constantly receiving warnings > > > saying "could not allocate memory" > This is an ffmpeg error message. Just a simple grep returns (among other > things): > > https://github.com/mpc-hc/FFmpeg/blob/master/libavutil/internal.h#L133
# av_log(ctx, AV_LOG_ERROR, "Cannot allocate memory.\n");\ "Cannot" and "could not" are not the same thing. Accuracy is paramount when quoting error messages. > Full output and other, more detailed information in this gist: > https://gist.github.com/nedrocks/09afd6a4fa2cd472f17a > > ffmpeg -y -ss 0.846 -i /tmp/f5543c87-77f5-466a-9f9f-4ba8b40fae03.webm -ss > 1.863 -i /tmp/f6cf2730-bfb3-40e5-aef6-3a03ca24333d.webm -filter_complex > '[0:v]pad=640*2:480[left];[left][1:v]overlay=x=640+(640-w)/2:y=(480-h)/2;amix' Having two unconnected graphs in the same graph is not a good idea. And try using amerge+pan instead of amix; amix may have scheduling problems that could explain a huge memory consumption. Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
