[FFmpeg-devel] H.261 and H.263 RTP broken?

Georges-Etienne Legendre legege
Sun Jan 25 04:29:53 CET 2009


Hi all,

I try to stream an H.263 video over RTP (ffmpeg SVN-r16766).
$ ffmpeg -i video.mov -an -vcodec h263 -s qcif -re -f rtp rtp:// 
localhost:5000

SDP:
v=0
o=- 0 0 IN IP4 127.0.0.1
t=0 0
s=No Name
a=tool:libavformat 52.25.0
c=IN IP4 localhost
m=video 5000 RTP/AVP 34
b=AS:200

On the other side, I use ffplay to view the outcome, but It doesn't  
work really well.
$ ffplay video.h263.sdp

Here is the outcome. On screen, the video is shown with broken frames.

FFplay version SVN-r16766, Copyright (c) 2003-2009 Fabrice Bellard, et  
al.
   configuration: --prefix=/usr/local/ffmpeg --extra-cflags=-I/usr/ 
local/x264/include --extra-ldflags=-L/usr/local/x264/lib --disable- 
vhook --enable-shared --enable-pthreads --disable-mmx --cc=gcc-4.0 -- 
enable-gpl --enable-libx264
   libavutil     49.14. 0 / 49.14. 0
   libavcodec    52.11. 0 / 52.11. 0
   libavformat   52.25. 0 / 52.25. 0
   libavdevice   52. 1. 0 / 52. 1. 0
   built on Jan 24 2009 20:41:08, gcc: 4.0.1 (Apple Inc. build 5484)
[h263 @ 0x103b800]illegal ac vlc code at 3x3
[h263 @ 0x103b800]Error at MB: 39
[h263 @ 0x103b800]concealing 99 DC, 99 AC, 99 MV errors
[h263 @ 0x103b800]illegal ac vlc code at 3x3
[h263 @ 0x103b800]Error at MB: 39
[h263 @ 0x103b800]concealing 99 DC, 99 AC, 99 MV errors
2009-01-24 22:13:21.687 ffplay[93614:10b] Warning once: This  
application, or a library it uses, is using NSQuickDrawView, which has  
been deprecated. Apps should cease use of QuickDraw and move to Quartz.
[h263 @ 0x103b800]Bad picture start code
[h263 @ 0x103b800]header damaged
[h263 @ 0x103b800]Bad picture start code
[h263 @ 0x103b800]header damaged
[h263 @ 0x103b800]illegal ac vlc code at 6x4
[h263 @ 0x103b800]Error at MB: 54
[h263 @ 0x103b800]concealing 99 DC, 99 AC, 99 MV errors
[h263 @ 0x103b800]Bad picture start code
[h263 @ 0x103b800]header damaged
[h263 @ 0x103b800]illegal ac vlc code at 5x4
[h263 @ 0x103b800]Error at MB: 53
...

It's similar for h261. But, it works for h264 with libx264.
Is this a known issue? Any thoughts?
-- 
Georges-Etienne Legendre





More information about the ffmpeg-devel mailing list