[Bug 739419] rtspsrc: not-linked after a while
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Fri Jul 10 10:32:11 PDT 2015
https://bugzilla.gnome.org/show_bug.cgi?id=739419
--- Comment #38 from Nicola <lists at svrinformatica.it> ---
so usually rtp buffers with wrong payload are received from gstssrcdemux and
dropped before rtpdemux, but after a gap if we have no luck and receive a
buffer with wrong payload it go to rtpdemux new caps are emitted and so not
linked error
as you can see here:
0:43:04.843385004 14857 0x7f16c4002850 DEBUG rtpptdemux
gstrtpptdemux.c:274:gst_rtp_pt_demux_get_caps: pt 112, got caps
application/x-rtp, media=(string)video, payload=(int)96, clock-rate=(int)90000,
encoding-name=(string)H264, profile-level-id=(string)4D0014,
packetization-mode=(string)0,
sprop-parameter-sets=(string)"Z01AKIuVAPAET8sIAABdwAAK/IQg\,aP44gA\=\=",
ssrc=(uint)826811416, npt-start=(guint64)0, play-speed=(double)1,
play-scale=(double)1
we are accepting caps with payload 96 for a buffer with payload 112, it is ok
for you not emitting the new caps signal in this case and drop the buffer in
the rtpdemux? Or have I to find another way?
--
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