I guess this thread needs an update. On latest ffmpeg (3.4.1) I get:
$ time ffmpeg -y -f lavfi -i nullsrc=s=hd720:d=600 -preset ultrafast out.mp4
real 0m26.578s
$ time ffmpeg -y -f lavfi -i nullsrc=s=hd720:d=600 -movflags +faststart -preset ultrafast out.mp4
real 0m26.849s
Same results. Now try with a real video:
$ time ffmpeg -y -i Sintel.2010.1080p.mp4 -preset:v ultrafast out.mp4
real 3m38.829s
$ time ffmpeg -y -i Sintel.2010.1080p.mp4 -preset:v ultrafast -movflags +faststart out.mp4
real 3m43.674s
About 2% difference, that could be just noise.
Also need to note that "Starting second pass: moving the moov atom to the beginning of the file" phase took no more than couple seconds on 600Mb output file.
I did notice a second pass, but I didn't think it would take that long. Nice to know. – Sun – 2014-12-24T21:52:57.873
@sunk818 The time will of course vary depending on your input. – llogan – 2014-12-24T22:19:00.847
In the latest version of ffmpeg (3.x+ or 4.x+), the correct syntax is
– Siu Ching Pong -Asuka Kenji- – 2018-12-23T14:59:04.697-movflags faststart
indeed (without the+
sign). See: https://ffmpeg.org/ffmpeg-formats.html#Options-8@SiuChingPong-AsukaKenji- It doesn't really matter if you include the
– llogan – 2018-12-26T00:17:46.893+
or not.