[Bug 739419] rtspsrc: not-linked after a while

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Tue Dec 20 22:58:26 UTC 2016


https://bugzilla.gnome.org/show_bug.cgi?id=739419

--- Comment #65 from Nicola <lists at svrinformatica.it> ---
As principle I agree but looking at the logs seems not so simple, please take a
look here, this is what happen when a new payload type arrive on the same SSRC,
the right payload is 112 the good one is 96

rtpsource rtpsource.c:1158:update_receiver_stats: seq 42118, PC: 1, OC: 0
rtpsource rtpsource.c:938:calculate_jitter: SSRC 75699a4c got payload 112
rtpsource rtpsource.c:898:get_clock_rate: new payload 112
rtpbin gstrtpbin.c:3232:pt_map_requested:<manager> payload map requested for pt
112 in session 0
rtpbin gstrtpbin.c:937:get_pt_map: searching pt 112 in cache
rtpbin gstrtpbin.c:950:get_pt_map: emiting signal for pt 112 in session 0
rtspsrc gstrtspsrc.c:2645:request_pt_map:<rtspsrc0> getting pt map for pt 112
in session 0
rtpbin gstrtpbin.c:1915:_gst_caps_accumulator: got caps (NULL)
rtpbin gstrtpbin.c:1915:_gst_caps_accumulator: got caps (NULL)
rtpbin gstrtpbin.c:1001:get_pt_map: no pt map could be obtained
rtpbin gstrtpbin.c:3243:pt_map_requested:<manager> could not get caps
rtpsession gstrtpsession.c:1597:gst_rtp_session_get_caps_for_pt:<rtpsession0>
could not get caps
rtpsession rtpsession.c:1420:source_clock_rate: got clock-rate -1 for pt 112
rtpsource rtpsource.c:910:get_clock_rate: got clock-rate -1
rtpsource rtpsource.c:983:calculate_jitter: cannot get clock-rate for pt 112
rtpsource rtpsource.c:873:push_packet: pushing queued packet
rtpsession rtpsession.c:1389:source_push_rtp: source 75699a4c pushed receiver
RTP packet

so in rtspsrc getting pt map return NULL caps (unknown_stream) but this rtp
packet is pushed anyway, do you agree that this packet should be dropped?
rtspsrc seems to do the right thing, it says "hey I don't know this rtp packet"
but the buffer should be dropped elsewhere, probably in rtpsource, do you
agree?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list