videorate: Don't forget last_ts on caps changes

Whenever that caps changes does not imply that a new segment will start.
Don't reset the last_ts if only the caps have changed. This fixes issues
if you have a stream without only first frame with TS=0, and have resolution
change happening. This was a regression introduced by !3059, which issue was
described in #1352. The reported issue is still fix after this change.

Fixes #1034

Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/5712>

diff --git a/subprojects/gst-plugins-base/gst/videorate/gstvideorate.c b/subprojects/gst-plugins-base/gst/videorate/gstvideorate.c
index c41b6fa..4a09730 100644 (file)
--- a/subprojects/gst-plugins-base/gst/videorate/gstvideorate.c
+++ b/subprojects/gst-plugins-base/gst/videorate/gstvideorate.c
@@ -1650,7 +1650,6 @@ gst_video_rate_transform_ip (GstBaseTransform * trans, GstBuffer * buffer)
         " after receiving caps");
     gst_video_rate_swap_prev (videorate, NULL, GST_CLOCK_TIME_NONE);
     gst_clear_caps (&videorate->prev_caps);
-    videorate->last_ts = GST_CLOCK_TIME_NONE;
     videorate->average = 0;
   }