GNOME Bugzilla – Bug 785027
videorate: Outputs too much data on segment updates
Last modified: 2018-11-03 11:57:59 UTC
When an "update" segment arrives in videorate, the next timestamps is resetted, causing a huge amount of duplicate (and late) frames to be outputted. To reproduce, using the gst-validate media suite: gst-launch-1.0 -v uridecodebin uri=file://$HOME/gst-validate/gst-integration-testsuites/medias/defaults/mp4/fragmented_nonseekable_sink.mp4 ! identity name=before silent=False ! videorate ! fakesink name=after silent=False What comes in to videorate: * segment start:0, stop:2s * buffers from 0 to 2s * segment start:0, stop:4s * buffers from 2s to 4s * etc... What comes out of videorate * segment start:0 stop:2s * buffers from 0 to 2s * segment start:0, stop:4s * buffers from 0 to 2s /!\ ** The problem is right here. Those buffers are all duplicates of the incoming 2s buffer and are all late. * buffers from 2s to 4s Any element after videorate that assumes that timestamps are increasing is going to have a looot of problems.
Created attachment 355801 [details] [review] check: Add test for videorate segment update handling
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/367.