By default ffmpeg sends a whole lotta messages to stderr: when built, how built, codecs, etc, etc, etc.

How can I make it quieter?

I've tried -v 0 (and -v 10 since the documentation just coyly says Set the logging verbosity level. with no indication of what the range of inputs is) -- still not quiet.

I've tried -loglevel quiet -- still not quiet.

I should mention, I'm looking for "quieter," not "no output ever". If there's an error I want to see it, but I don't need to hear about ffmpeg's configuration every. single. time.

link|improve this question

80% accept rate
ffmpeg is definitely one of those 'for developers, by developers' kinds of programs. – digitxp Aug 22 '11 at 22:10
feedback

2 Answers

up vote 3 down vote accepted

I haven't tested it out, but I see an option in the man page to do:

ffmpeg -loglevel panic [rest of your ffmpeg stuff]

Should make it so only serious errors are logged, in theory

link|improve this answer
Sweet fancy Moses! It works! You have no idea how much seeing ffmpeg's configuration you've just saved me. – blahdiblah Jan 12 at 6:54
Even with -loglevel panic, for me it's only reducing output a little - it still prints version information, stream mapping, configuration options, (and even progress information!).... any ideas? I might have to mention that it's a self-compiled version from latest svn trunk. – nyarlathotep Apr 30 at 11:42
feedback

This is a little cheap to go about it, but appending >/dev/null 2>&1 is a sure way to keep ffmpeg silent in the shell.

Example

ffmpeg -f x11grab -y -r 24 -s 800x600 -i :0.0+1366,100 -f oss -i /dev/dsp3 -sameq ./out.avi >/dev/null 2>&1

More info about bash output

link|improve this answer
1  
Except that ffmpeg is one step ahead of you, and outputs both configuration information and actual errors to stderr. – blahdiblah Aug 23 '11 at 19:19
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.