rtpbasepayload: timestamp bug, if rate control=no
authorKristofer Björkström <kristofb@axis.com>
Thu, 23 Jan 2020 15:11:28 +0000 (16:11 +0100)
committerGStreamer Merge Bot <gitlab-merge-bot@gstreamer-foundation.org>
Tue, 11 Feb 2020 12:30:49 +0000 (12:30 +0000)
commit4152b0c840c608e0cba16f117a8a279d5e8642f6
treeac46b6c47eb51adfb718d0748d1513b5b1d214a1
parent1e9da26b685c666bfb59a461dc65b936c4cbb8cb
rtpbasepayload: timestamp bug, if rate control=no

With commit "basepayload: Expose onvif-no-rate-control property" the rtp
timestamp changed behaviour when rate control is disabled.

When disabling rate control, we must take care of the stream time to
avoid the timestamps to begin from zero again.
gst-libs/gst/rtp/gstrtpbasepayload.c
tests/check/libs/rtpbasepayload.c