[Bug 751026] New: rtpjitterbuffer: calculate elapsed timed base on only clock base time

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 751026
           Summary: rtpjitterbuffer: calculate elapsed timed base on only
                    clock base time
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: All
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: zzoon.ko at samsung.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

In case that rtsp server sends range info in play response msg as below (start
not 0), rtpjitterbuffer is mis-calculating elapsed time.

RTSP response message 0xb63f8030
 status line:
   code:   '200'
   reason: 'OK'
   version: '1.0'
 headers:
   key: 'CSeq', value: '5'
   key: 'RTP-Info', value:
'url=rtsp://127.0.0.1:8554/test/stream=0;seq=29781;rtptime=2982392158,
url=rtsp://127.0.0.1:8554/test/stream=1;seq=2244;rtptime=3012487835'
   key: 'Range', value: 'npt=29.375027216-62.95'
   key: 'Server', value: 'GStreamer RTSP server'
   key: 'Session', value: 'eyblXfy01$zjO-+Z'
 body: length 0


This causes EOS event finally, and pipeline is shutdown very soon. 
Because mis-calculated elapsed time leads to adding EOS timer in
update_estimated_eos and do_eos_timeout creates EOS event.

IMHO, elapsed time needs to be calculated based on clock base time and npt
start time.

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