[FFmpeg-trac] #6928(ffmpeg:new): Output log messaging is impractical, either nothing, or spammed messages

FFmpeg trac at avcodec.org
Mon Dec 25 06:34:21 EET 2017


#6928: Output log messaging is impractical, either nothing, or spammed messages
----------------------------------+--------------------------------------
             Reporter:  ZexaronS  |                     Type:  defect
               Status:  new       |                 Priority:  minor
            Component:  ffmpeg    |                  Version:  git-master
             Keywords:  log       |               Blocked By:
             Blocking:            |  Reproduced by developer:  0
Analyzed by developer:  0         |
----------------------------------+--------------------------------------
 Summary of the bug:

 If I set the loglevel to warning or error, the log output is empty, if I
 set the loglevel to info or verbose, I always get the full detailed
 reports of this filter message, there is nothing in-between that would get
 me just the progress updates without these messages.

 As the subtitles get overlaid over the video, it's producing these
 messages, however the output is fine.

 This message should go into the debug or trace category since it's not a
 warning and not an error and doesn't even talk about anything going wrong,
 the results are successful, so it's not informing anything, and since it's
 going to prevent any progress from showing, I think it doesn't even count
 for verbose.

 THE MESSAGE IS:
 ''Changing frame properties on the fly is not supported by all filters.''


 I had an idea for long now that loging in ffmpeg should be improved in
 many areas. These points below should be considered seriously, even if
 this one message is handled and moved to debug or trace or whatever, I
 still would like to see the actual logging logic overhauled for any future
 such messages or circumstances.

 1. An option should be created that truncates all these repeating messages
 and simply keeps driving the count number up to some acceptably high value
 (int32 maxvalue) instead of a fixed time delay which currently sits around
 a few 100 miliseconds or so, it's still enough on a long 2-3 hour haul
 that it exceeds the commandprompt buffer on windows (win7, didn't try in
 win10)

 2. The default timer for repriting the same message could simply be
 increased. Or even better, it could be based on the loglevel, the lesser
 the severity the more delay would there be before same message and the
 repeated message counter is reprinted.

 3. The realtime repeated message counter would be removed and replaced
 with the progress line instead, the counter would count-up hiddenly and
 would just print to the log above without interferring with the realtime
 progress indicators.

 I had more ideas but those are probably more suitable for another ticket,
 if I have something substantial around this I will comment later, but
 probably this isn't the place to discuss various other things regarding
 messaging, unless someone corrects me.


 {{{
 ffmpeg version git-2017-12-23-9e5e323 Copyright (c) 2000-2017 the FFmpeg
 developers
   built with gcc 7.2.0 (GCC)
   configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-
 bzlib --enable-fontconfig --enable-gnutls --enable-iconv --
 enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame
 --enable-libopencore-amrnb --enable-libopencore-amrwb --
 enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy
 --enable-libsoxr --enable-libtheora --enable-libtwolame -
 -enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264
 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-l
 zma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis
 --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex
  --enable-amf --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc
 --enable-dxva2 --enable-avisynth --enable-libmfx
   libavutil      56.  6.100 / 56.  6.100
   libavcodec     58.  8.100 / 58.  8.100
   libavformat    58.  3.100 / 58.  3.100
   libavdevice    58.  0.100 / 58.  0.100
   libavfilter     7.  7.100 /  7.  7.100
   libswscale      5.  0.101 /  5.  0.101
   libswresample   3.  0.101 /  3.  0.101
   libpostproc    55.  0.100 / 55.  0.100
 Input #0, matroska,webm, from 'Biografija_2017.11.26_06.30.tmpmkv':
   Metadata:
     ENCODER         : Lavf58.3.100
   Duration: 01:00:01.53, start: 0.000000, bitrate: 10205 kb/s
     Stream #0:0: Video: mpeg2video (Main), yuv420p(tv, progressive),
 1920x1080 [SAR 1:1 DAR 16:9], 25 fps, 25 tbr, 1k tbn, 50 tbc
 (default)
     Metadata:
       ENCODER         : Lavc58.8.100 mpeg2video
       DURATION        : 01:00:00.520000000
     Stream #0:1(eng): Audio: mp2, 48000 Hz, stereo, s16p, 192 kb/s
 (default)
     Metadata:
       DURATION        : 01:00:00.072000000
     Stream #0:2(slv): Subtitle: dvb_subtitle (default)
     Metadata:
       DURATION        : 01:00:01.528000000
 File 'Biografija_2017.11.26_06.30.mkv' already exists. Overwrite ? [y/N] y
 Stream mapping:
   Stream #0:0 (mpeg2video) -> overlay:main
   Stream #0:2 (dvbsub) -> overlay:overlay
   overlay -> Stream #0:0 (libx264)
   Stream #0:1 -> #0:1 (copy)
 Press [q] to stop, [?] for help
 [matroska,webm @ 00000000005627e0] sub2video: using 1920x1080 canvas
 [libx264 @ 0000000000597280] using SAR=1/1
 [libx264 @ 0000000000597280] using cpu capabilities: MMX2 SSE2Fast SSSE3
 SSE4.2 AVX
 [libx264 @ 0000000000597280] profile High, level 4.0
 [libx264 @ 0000000000597280] 264 - core 152 r2851 ba24899 - H.264/MPEG-4
 AVC codec - Copyleft 2003-2017 - http://www.videolan.org/
 x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex
 subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 c
 hroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1
 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=
 0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0
 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 ope
 n_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0
 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0
  qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
 Output #0, matroska, to 'Biografija_2017.11.26_06.30.mkv':
   Metadata:
     encoder         : Lavf58.3.100
     Stream #0:0: Video: h264 (libx264) (H264 / 0x34363248), yuv420p,
 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 25 fps, 1k tbn, 25 tbc
  (default)
     Metadata:
       encoder         : Lavc58.8.100 libx264
     Side data:
       cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
     Stream #0:1(eng): Audio: mp2 (P[0][0][0] / 0x0050), 48000 Hz, stereo,
 s16p, 192 kb/s (default)
     Metadata:
       DURATION        : 01:00:00.072000000
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 17 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 23 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 19 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 20 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 23 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 20 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 24 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 23 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 23 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 22 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 23 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 22 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 19 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 23 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 24 times
 [graph 0 input from stream 0:2 @ 0000000000599940] Changing frame
 properties on the fly is not supported by all filters.
     Last message repeated 22 times
 }}}

 {{{
 % for %%F in (*.tmpmkv) do ffmpeg -loglevel info -i "%%~F" -preset medium
 -crf 23 -vcodec libx264 -filter_complex "[0:v][0:s:0]overlay[v]" -map
 "[v]" -x264-params no-deblock -pix_fmt yuv420p -map 0:a:0 -acodec copy
 -threads 0 -f matroska "%%~nF.mkv"
 ffmpeg version git-2017-12-23-9e5e323
 built on ... gcc 7.2.0 (GCC)
 }}}
 Patches should be submitted to the ffmpeg-devel mailing list and not this
 bug tracker.

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


More information about the FFmpeg-trac mailing list