[FFmpeg-trac] #2476(undetermined:new): Unexpected output when using -v and -report

FFmpeg trac at avcodec.org
Thu Apr 18 06:25:04 CEST 2013


#2476: Unexpected output when using -v and -report
-------------------------------------+-------------------------------------
               Reporter:  dericed    |                  Owner:
                   Type:  defect     |                 Status:  new
               Priority:  normal     |              Component:
                Version:  git-       |  undetermined
  master                             |               Keywords:  verbosity
             Blocked By:             |               Blocking:
Reproduced by developer:  0          |  Analyzed by developer:  0
-------------------------------------+-------------------------------------
 Summary of the bug:

 I would like to run ffmpeg with verbosity set to warning but also make use
 of the -report option.

 When I run with only the -v warning option I get the desired brief output.

 {{{
 ffmpeg -v warning -f lavfi -i mandelbrot -t 10 -y -stats test.mpeg
 [mpeg @ 0x7f9c8c02a800] VBV buffer size not set, muxing may fail
 frame=  234 fps= 66 q=31.0 size=     782kB time=00:00:09.28 bitrate=
 690.3kbits/s
 }}}

 When I add -report then the verbose report is generated, but also the
 terminal output becomes more verbose (from 2 lines of output to 14):

 {{{
 ffmpeg -report -v warning -f lavfi -i mandelbrot -t 10 -y -stats test.mpeg
 ffmpeg version 1.1.git Copyright (c) 2000-2013 the FFmpeg developers
   built on Apr 15 2013 23:36:08 with Apple LLVM version 4.2
 (clang-425.0.27) (based on LLVM 3.2svn)
   configuration: --prefix=/usr/local/Cellar/ffmpeg/HEAD --enable-shared
 --enable-pthreads --enable-gpl --enable-version3 --enable-nonfree
 --enable-hardcoded-tables --enable-avresample --enable-vda --cc=cc --host-
 cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-
 libmp3lame --enable-libxvid --enable-ffplay --enable-libcaca --enable-
 libopenjpeg --extra-
 cflags='-I/usr/local/Cellar/openjpeg/1.5.1/include/openjpeg-1.5 '
   libavutil      52. 26.100 / 52. 26.100
   libavcodec     55.  2.100 / 55.  2.100
   libavformat    55.  2.100 / 55.  2.100
   libavdevice    55.  0.100 / 55.  0.100
   libavfilter     3. 56.101 /  3. 56.101
   libavresample   1.  1.  0 /  1.  1.  0
   libswscale      2.  2.100 /  2.  2.100
   libswresample   0. 17.102 /  0. 17.102
   libpostproc    52.  3.100 / 52.  3.100
 [mpeg @ 0x7fb27282ea00] VBV buffer size not set, muxing may fail
 frame=  234 fps= 66 q=31.0 size=     830kB time=00:00:09.96 bitrate=
 682.7kbits/s
 }}}

 I propose that use of -report and -v together use the verbosity level set
 by -v for terminal output, but use the standard reporting verbosity (info,
 IIRC) for the generated log, like this:

 {{{
 ffmpeg -report -v warning -f lavfi -i mandelbrot -t 10 -y -stats test.mpeg
 [mpeg @ 0x7f9c8c02a800] VBV buffer size not set, muxing may fail
 frame=  234 fps= 66 q=31.0 size=     782kB time=00:00:09.28 bitrate=
 690.3kbits/s
 }}}

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2476>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list