18
7
I tired running 8 commands in parallel to fully utilize the CPU and speed up Video conversions, something like this:
ffmpeg -i input.mp4 -t 60 -f mp4 /mnt/a.mp4 > /dev/null 2>&1 &
ffmpeg -i input.mp4 -t 60 -f mp4 /mnt/b.mp4 > /dev/null 2>&1 &
ffmpeg -i input.mp4 -t 60 -f mp4 /mnt/c.mp4 > /dev/null 2>&1 &
ffmpeg -i input.mp4 -t 60 -f mp4 /mnt/d.mp4 > /dev/null 2>&1 &
ffmpeg -i input.mp4 -t 60 -f mp4 /mnt/e.mp4 > /dev/null 2>&1 &
ffmpeg -i input.mp4 -t 60 -f mp4 /mnt/f.mp4 > /dev/null 2>&1 &
ffmpeg -i input.mp4 -t 60 -f mp4 /mnt/g.mp4 > /dev/null 2>&1 &
ffmpeg -i input.mp4 -t 60 -f mp4 /mnt/h.mp4 > /dev/null 2>&1 &
2 to 3 of them get stopped. Why does this happen? Is this a FFmpeg limitation? I have tried this on 16 core and 4 core machines, EC2 c1.xlarge and cc2.8xlarge. Same behavior. I have tried complicated commands and simple ones, still same, 2 or 3 get stopped.
Did you find any parameter for using multi processors?! – Dr.jacky – 2015-08-19T04:45:16.660
what do you mean by "get stopped" here? bash shows them as paused? – rogerdpack – 2016-01-31T04:33:10.413
3To my knowledge there shouldn't be anything in FFmpeg itself stopping you from doing so. Could be a shell issue? – slhck – 2013-01-18T11:28:11.517
What if I have different inputs for each command? How can I make them independent, because if one stops they all stop. – Samson – 2013-08-09T09:39:53.993