[FFmpeg-trac] #1687(FFmpeg:open): -v quiet -stats
FFmpeg
trac at avcodec.org
Tue Aug 28 01:17:47 CEST 2012
#1687: -v quiet -stats
------------------------------------+----------------------------------
Reporter: gd2shoe | Owner:
Type: defect | Status: open
Priority: minor | Component: FFmpeg
Version: git-master | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
------------------------------------+----------------------------------
Comment (by gd2shoe):
Replying to [comment:3 Cigaes]:
> The {{{-stats}}} option exists mostly for symmetry with the
{{{-nostats}}} option, because the options parsing code works that way.
Interesting.
> The default is {{{-stats}}}, so it has no effect.
Part of my point. It makes little to no sense to have an option that does
nothing whatsoever.
> The stats go through the logging mechanism, and as such are subject to
the loglevel system, regardless of the {{{-stats}}} option.
It is this idea that I wish to challenge. If -stats appears on the
command line, it is because the user explicitly wants that particular
output, regardless of logging level.
Is there any reason to think otherwise?
Frankly, I don't see why the progress meter must be fixed at the info
level. Why can't it exist at info by default? Why can't -stat move
progress to the current log level? Especially if attached to a tty?
If that sounds stupid, then why can't -stat change from logging to stderr?
Or why can't there be another option to suppress non-progress output. (It
makes more sense to me to fix and reuse the option that is already there--
but worthless-- than to invent a new one, but it would fit the bill.)
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1687#comment:4>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list