RTP handling and clock-rates

Sebastian Dröge sebastian at centricular.com
Mon Apr 18 07:13:07 UTC 2016

On Do, 2016-04-14 at 17:20 +0000, Jon Mandrell wrote:
> I am using gstreamer 1.2 (the same thing happens with 1.6). I am
> attempting to tune to an RTP stream provided by an external device,
> and I'm using the following pipeline as a test:
> GST_DEBUG=*:2 gst-launch-1.0 -v udpsrc multicast-iface=eth2 buffer-
> size=8000000 do-timestamp=true uri=udp:// !
> application/x-rtp,media=video,clock-rate=90000 ! rtpbin ! fakesink
> silent=false
> I do see packets coming out of the fakesink, but I'm also getting the
> following message logged between every packet:
> 0:00:00.328454488 12399  0x84aa260 WARN               rtpsource
> rtpsource.c:994:calculate_jitter: cannot get clock-rate for pt 33
> How do I let it know the clock-rate? I had hoped providing the
> capsfilter would handle that.

Your caps are not complete, try providing at least the PT in there too.
Alternatively there is the request-pt-map signal on rtpbin where you
can provide the caps on demand, but that requires writing code.

Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160418/1afcd5be/attachment.sig>

More information about the gstreamer-devel mailing list