[Bug 785027] New: videorate: Outputs too much data on segment updates
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Mon Jul 17 14:57:43 UTC 2017
https://bugzilla.gnome.org/show_bug.cgi?id=785027
Bug ID: 785027
Summary: videorate: Outputs too much data on segment updates
Classification: Platform
Product: GStreamer
Version: git master
OS: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gst-plugins-base
Assignee: gstreamer-bugs at lists.freedesktop.org
Reporter: bilboed at bilboed.com
QA Contact: gstreamer-bugs at lists.freedesktop.org
GNOME version: ---
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list