Re: [FFmpeg-trac] #285(avformat:closed): RTSP h264 video stream always reports corrupted macroblock

[FFmpeg]

#285: RTSP h264 video stream always reports corrupted macroblock
-+
 Reporter:  bovine   |Owner:  michael
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  avformat
  Version:  unspecified  |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by Ph0t0n):

 I did some online research today because I am still seeing similar errors.
 Back in 2011 a fix to the UDP code was contributed that made a huge
 improvement, but I don't think it's completely fixed. I have run quite a
 few streams now that exhibit a slight "smearing" issue.  It appears to
 occur in higher resolution videos and whenever a network connection isn't
 absolutely pristine.

 The reason I believe ffmpeg's RTSP UDP mode is still broken is because
 other libraries are able to play the streams without the issues. VLC for
 instance uses Lib555. I have found several groups online that solved the
 issue by switching to a different RTSP library.  The majority of people
 seem to be solving it by switching to TCP, but that pretty much defeats
 the whole purpose of RTSP and it increases latency.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #285(avformat:closed): RTSP h264 video stream always reports corrupted macroblock

[FFmpeg]

#285: RTSP h264 video stream always reports corrupted macroblock
-+
 Reporter:  bovine   |Owner:  michael
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  avformat
  Version:  unspecified  |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by rogerdpack):

 maybe rtsp should default to tcp, these corruptions seem to confuse... [?]

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #285(avformat:closed): RTSP h264 video stream always reports corrupted macroblock

[FFmpeg]

#285: RTSP h264 video stream always reports corrupted macroblock
-+
 Reporter:  bovine   |Owner:  michael
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  avformat
  Version:  unspecified  |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+

Comment (by andrewc):

 It seems for me at least this issue is not fully resolved with Geovision
 GV-FE420.

 However there does seem to be a workaround. If you've got a GV-FE420 and
 are still having issues with frame corruption (as I am with ffmpeg 0.10.2)
 then try prepending ?tcp to the RTSP URL.

 eg: Source Path: rtsp://admin:admin@##.##.##.##:8554/CH001.sdp?tcp (or
 whatever your username/password is.)

 Apparently the "?tcp" suffix is an argument parsed and recognized by
 ffmpeg to not use udp, which currently tends to cause frame corruption due
 to udp read buffer bug.

 From http://www.zoneminder.com/wiki/index.php?title=Geovision.

 So far it seems to be working for me. Although I still need to test the
 cam with higher frame rates, which I can only do tomorrow when onsite.

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #285(avformat:closed): RTSP h264 video stream always reports corrupted macroblock

[FFmpeg]

#285: RTSP h264 video stream always reports corrupted macroblock
-+
 Reporter:  bovine   |Owner:  michael
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  avformat
  Version:  unspecified  |   Resolution:  fixed
 Keywords:   |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+
Changes (by cehoyos):

 * status:  new => closed
 * resolution:   => fixed
 * component:  FFmpeg => avformat


Comment:

 Thank you for the confirmation, if you find other bugs, please open a new
 ticket!

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac