On Thu, 30 Apr 2015 18:06:03 +0800 Kai Hendry <[email protected]> wrote:
> Wow, so you've not seen a -report like this? > http://s.natalian.org/2015-04-30/ffmpeg-20150430-102645.log The -report option creates an output using the "verbose" loglevel resulting in such a large output. It is often overly verbose for general help and most of the time is detrimental due to the extra noise. This behavior can be changed with the FFREPORT environmental variable. This example will use the "info" loglevel, which is the default loglevel, and output the log to "ffreport.log". FFREPORT=file=ffreport.log:level=32 ffmpeg -i input output (Yes, it would be nice if the level option used the human names – patch welcome). Refer to -loglevel and -report in the ffmpeg manual for more info. Alternatively you could redirect the output to a file: ffmpeg -i input output 2>&1 | tee ffoutput.log tee is used in this example so you can see the output in your console *and* save it to a file (Bash 4+ users can use '|&' instead of '2>&1 |'). Otherwise, if just using: ffmpeg -i input output > ffoutput.log 2>&1 ...there would be no output in your console and this could cause ffmpeg to hang if it is waiting for a response from you, such as confirming a output file overwrite, and anyway you could miss warnings, errors, etc. I don't know if any of this applies to Windows users. _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
