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

[GStreamer (GNOME Bugzilla)]

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

--- Comment #76 from Nicola <lists at svrinformatica.it> ---
(In reply to dashesy from comment #75)
> The not-linked error happens after quite some time sporadically, the fix
> needs your original patch (that I double checked and was applied). 

the not-linked error does not happen anymore for me with 1.10 and git master,
while it happens with 1.6 if I don't apply my old patch

> 
> My patch tries to fix this error:
> 
> 0:00:00.296884000  2872 000001BDAB2199C0 ERROR        rtpjitterbuffer
> gstrtpjitterbuffer.c:1372:gst_jitter_buffer_sink_parse_caps:
> <rtpjitterbuffer0> Got caps with wrong payload type (got 96, expected 112)
> 0:00:00.296884000  2872 000001BDAB2199C0 WARN         rtpjitterbuffer
> gstrtpjitterbuffer.c:3133:gst_rtp_jitter_buffer_chain:<rtpjitterbuffer0> No
> clock-rate in caps!, dropping buffer

has you can see the buffer is dropped anyway

> 
> 
> Even though 96 is declared in SDP (is valid) and 112 is invalid, one with
> pt=112 results in one buffer with pt=96 to be dropped.
> 

ok it is a bit late at my timezone, I'll check tomorrow

> 
> I will try your new patch on top of 1.10 and report.

in my test my patch is useless, the buffer is always dropped and so ptdemux has
no chance to get a buffer with a different payload and so to emit a signal, I
still think that if such buffer is not dropped inside ptdemux it will cause a
not linked error (my old patch). 

The purpose of the latest patch is to do what Sebastian said and so to have
another suggestion on how to proceed

> The stream is private but I will gladly test.

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