[Bug 643591] New: next timestamp not properly initialized with new segments
bugzilla at gnome.org
Tue Mar 1 05:55:30 PST 2011
GStreamer | gst-ffmpeg | git
Summary: next timestamp not properly initialized with new
AssignedTo: gstreamer-bugs at lists.freedesktop.org
ReportedBy: cascardo at holoscopio.com
QAContact: gstreamer-bugs at lists.freedesktop.org
GNOME target: ---
GNOME version: ---
Created an attachment (id=182178)
When only invalid input timestamps arrive, output timestamps are based on
next_out, which is initialized as GST_CLOCK_TIME_NONE. This is usually not
inside the current segment. clip_audio_buffer will return TRUE for the first
buffer (which has an invalid timestamp), but will return FALSE for the next
buffers, since they use now next_out (with a value of the last timestamp plus
duration) as timestamp.
One of the bugs here is to set next_out as timestamp plus duration when
timestamp is invalid.
One solution is to use next_out as timestamp when timestamp is invalid, but set
next_out to the start of the segment, when a NEWSEGMENT event arrives.
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- 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