Regression in baseparse when PTS/DTS is incorrect from camera
fa831247 breaks for specific rtsp cameras where DTS/PTS (among other things) is strange and no framerate is deduced (vui parameters); Leading to buffers having no timestamp in downstream elements (videorate in this case):
0:00:05.988408060 6557 0x7f62b402c4f0 WARN videorate gstvideorate.c:1650:gst_video_rate_transform_ip:<appsinkrate> Got buffer with GST_CLOCK_TIME_NONE timestamp, discarding it
This manifests in appsink as if PTS fast-forwards for buffers, when pipeline clock is set to the realtime clock (not 100% sure if this has an effect).
I am working on a gst-launch-1.0 test to replicate, and will attach a gdppay of the rtsp stream promptly.