[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):

 Replying to [comment:3 michael]:
 > iam happy to look into this and fix it but how do i reproduce it ? is a
 account on wowza.server.com needed or can it be reproduced without this?

 I would think that a simple output to the local host via rtsp would
 exhibit the same behavior. I'll admit, I haven't had time to try. I'll see
 if I can get some details on that today. I'm hoping to have the patch
 submitted before that though. I have to review the latest HEAD as my
 rebase yesterday had some conflicts so we need to figure out what failed
 on the rebase first.

 > maybe some vlc/ffmpeg/whatever commands i can copy and paste to
 reproduce it ?

 This was all local client centric. I would imagine if you used the same
 command I posted in the ticket (with a local file as input) and output to
 a localhost rtsp port... you should see the same results in your terminal
 or wherever you're landing the output log via stderr.

 > I suspect fixing this if i can reproduce it would take me 5min but
 figuring out how to reproduce it well i dunno where to start :)

 I can appreciate that. Let me know if anything in my above comments
 doesn't jive and we can sync up on getting it reproduced.

 Again, I'm trying to get a patch submitted (I've just not had time to get
 it sent :( ) to solve this as well. It's tested and reports the output
 above. If anyone sees any problems with this please let me know.

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