[gst-devel] sending raw stream over rtp

Kocsis Tibor ikt011 at gmail.com
Wed Jan 5 09:07:41 CET 2011


Hi,

I have a basic rtsp server, and I try to use to send a raw stream to
the client. On the receiver side I use a simple gstreamer pipeline
like this: rtspsrc ! rtpvrawdepay ! xvimagesink. On the server there
are gstreamer elements, too, some source connected to a rtpvrawpay,
and to the gstrtpsink elements. The sending is started, and I can
watch something live view, but it is not fluency. These messages
appear on the client:

0:00:03.233100336 24189 0x7f654000bd20 WARN            rtpvrawdepay
gstrtpvrawdepay.c:378:gst_rtp_vraw_depay_process:<rtpvrawdepay0>
clipping length 540, offset 460
0:00:03.233134052 24189 0x7f654000bd20 WARN            rtpvrawdepay
gstrtpvrawdepay.c:378:gst_rtp_vraw_depay_process:<rtpvrawdepay0>
clipping length 1086, offset 278
0:00:03.233192201 24189 0x7f654000bd20 WARN            rtpvrawdepay
gstrtpvrawdepay.c:378:gst_rtp_vraw_depay_process:<rtpvrawdepay0>
clipping length 252, offset 556
0:00:03.233232346 24189 0x7f654000bd20 WARN            rtpvrawdepay
gstrtpvrawdepay.c:378:gst_rtp_vraw_depay_process:<rtpvrawdepay0>
clipping length 798, offset 374
...

What can it cause?

My guess was I missed from the sdp (or built it up wrong), but the
params I send over in the fmtp is the same as on the payloader's
source pad (width, height, sample, even as depth, but as I see depth
is not parsed on the client side). Btw my rtsp server works with
h264/mpeg4 fine, so the elements are correctly linked.

The full rtsp communication is here: http://pastebin.com/fC8MsJkx

Any idea is welcomed

Regards
Tibor




More information about the gstreamer-devel mailing list