[Bug 788777] New: rtpjitterbuffer/h264parse timestamp issue

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 788777
           Summary: rtpjitterbuffer/h264parse timestamp issue
    Classification: Platform
           Product: GStreamer
           Version: 1.x
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: lists at svrinformatica.it
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 361248
  --> https://bugzilla.gnome.org/attachment.cgi?id=361248&action=edit
logs that show the issue

In a pipeline like this:

rtspsrc ! rtph264depay ! h264parse ! ...

using rtsp over tcp can happen that rtspsrc outputs buffers with the same
timestamp, when this happen h264parse outputs buffer with invalid timestamps.

Please take a look at the attached logs, you can see:

rtpjitterbuffer.c:916:rtp_jitter_buffer_calculate_pts:[00m backwards
timestamps, using previous time

so different buffers with pts 0:15:23.020362975 are sended.

Not sure how to handle this case, we need to change rtpjitterbuffer or
h264parse?

This problem seems to happen only using rtsp over tcp, I'm unable to reproduce
it using rtsp over udp.

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