[Bug 739419] rtspsrc: not-linked after a while
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Wed Dec 28 16:15:23 UTC 2016
https://bugzilla.gnome.org/show_bug.cgi?id=739419
--- Comment #71 from Nicola <lists at svrinformatica.it> ---
I'm planning to migrate my gst base from 1.6 to 1.12 so I'm doing some more
accurate tests, this is what I see:
- gstreamer 1.6
1) with no patch applied rtspsrc errors out after a while
2) with the patch here I see the logs in the patch and streaming continue
- gstreamer 1.12 (git master)
I'm unable to reproduce the error, there are a lot of warning when pt change
but rtspsrc does not errors out, here are the warnings:
1) "rtpsource.c:983:calculate_jitter: cannot get clock-rate for pt 112", the
buffer is pushed anyway
2) "rtpjitterbuffer
gstrtpjitterbuffer.c:3133:gst_rtp_jitter_buffer_chain:<rtpjitterbuffer0> No
clock-rate in caps!, dropping buffer", the buffer is dropped here and never
arrive to ptdemux
the relevant change between 1.6 and git master is this one:
https://cgit.freedesktop.org/gstreamer/gst-plugins-good/commit/?id=608b4ee53c43c3dcbfee167349771eeffd92e071
if I apply this patch to 1.6 my old patch is not needed anymore,
dashey, why your patch is needed? In my tests the buffers are dropped anyway
since the caps refer to payload 96 and not 112 and so clock_rate is -1 and
gst_rtp_jitter_buffer_get_clock_rate return -1 too (request_pt_map return null
caps since pt 112 is not inside sdp). Is your stream different from the mine?
--
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