[FFmpeg-trac] #1446(undetermined:new): Output via rtsp results in logs not displaying frame size nor bitrate

[FFmpeg]

#1446: Output via rtsp results in logs not displaying frame size nor bitrate
-------------------------------------+-------------------------------------
             Reporter:  msmithng     |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  unspecified  |  undetermined
             Keywords:  rtsp rtmp    |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by msmithng):

 Thanks.

 I actually have a couple patches for ffmpeg.c and libavformat/utils.c that
 I need to submit for review.

 These produce accurate output data for each non-seekable output stream
 (there was a FIXME in ffmpeg.c: 'print_report' to address this...).
 Additionally it accurately tracks the amount of kBytes that have been
 shipped since the encode started.

 example output:

 {{{
 frame=  991 fps= 30 q=24.0 kB=  2299.2 kbps= 571.6 size=       0kB
 time=00:00:31.86 bitrate=   0.0kbits/s dup=1 drop=0
 frame= 1021 fps= 30 q=24.0 kB=  2369.8 kbps= 564.8 size=       0kB
 time=00:00:32.86 bitrate=   0.0kbits/s dup=1 drop=0
 frame= 1051 fps= 30 q=24.0 kB=  2438.7 kbps= 551.5 size=       0kB
 time=00:00:33.86 bitrate=   0.0kbits/s dup=1 drop=0
 frame= 1081 fps= 30 q=24.0 kB=  2504.6 kbps= 527.1 size=       0kB
 time=00:00:34.86 bitrate=   0.0kbits/s dup=1 drop=0
 frame= 1111 fps= 30 q=24.0 kB=  2574.6 kbps= 559.9 size=       0kB
 time=00:00:35.86 bitrate=   0.0kbits/s dup=1 drop=0
 }}}

 Granted, my interests lie in non-seekable output as I'm using this to
 stream live video. If there's a procedure that I need to follow to ensure
 that things work as expected for alternate outputs, please advise.

 I'll be honest, I'm not sure how well these additional fields are going to
 be received. We didn't want to mess with the {{{bitrate}}} entry since I
 figured others were probably using mechanisms that expected that to be
 there.

 I'll try to rebase tomorrow morning first thing and get these changes in
 for review.

 Judging by the above, do you have any comments that can be shared with me
 now?

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1446#comment:4>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker