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

[GStreamer (GNOME Bugzilla)]

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

--- Comment #58 from dashesy <dashesy at gmail.com> ---
This patch now also needs some change in `gstrtpjitterbuffer.c` to work. 

Because this block changes the pt to the new *Wrong* pt:

  if (G_UNLIKELY (priv->last_pt != pt)) {
    GstCaps *caps;

    GST_DEBUG_OBJECT (jitterbuffer, "pt changed from %u to %u", priv->last_pt,
        pt);

    priv->last_pt = pt;
    /* reset clock-rate so that we get a new one */
    priv->clock_rate = -1;

    /* Try to get the clock-rate from the caps first if we can. If there are no
     * caps we must fire the signal to get the clock-rate. */
    if ((caps = gst_pad_get_current_caps (pad))) {
      gst_jitter_buffer_sink_parse_caps (jitterbuffer, caps, pt);
      gst_caps_unref (caps);
    }
  }


Which results in this error:

0:00:00.358131000  2668 0000016BDADDD9C0 WARN               rtpsource
rtpsource.c:983:calculate_jitter: cannot get clock-rate for pt 112
0:00:00.359132000  2668 0000016BDADDD9C0 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.359132000  2668 0000016BDADDD9C0 WARN         rtpjitterbuffer
gstrtpjitterbuffer.c:3133:gst_rtp_jitter_buffer_chain:<rtpjitterbuffer0> No
clock-rate in caps!, dropping buffer
0:00:00.359132000  2668 0000016BDADDD9C0 WARN         rtpjitterbuffer
gstrtpjitterbuffer.c:3133:gst_rtp_jitter_buffer_chain:<rtpjitterbuffer0> No
clock-rate in caps!, dropping buffer


But If the above check would not change the last_pt to pt the patch in this bug
will result in dropping the buffer in `gstrtpdemux.c`.

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