RTP handling and clock-rates

[jmandrell]

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://226.0.0.11:2400 ! 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.​

Jon Mandrell
Software Manager
Zodiac Inflight Innovations
[hidden email]

11747 NE 1st, Suite 210
Bellevue, WA 98005 USA
P: 206-641-7184 | M: 206-999-1774
http://www.imsco-us.com

---

This email and any files transmitted with it are confidential & proprietary to Systems and Software Enterprises, LLC. This information is intended solely for the use of the individual or entity to which it is addressed. Access or transmittal of the information contained in this e-mail, in full or in part, to any other organization or persons is not authorized.

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Sebastian Dröge-3]

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://226.0.0.11:2400 !
> 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

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel