[Bug 750027] concat: Reset internal start offset to 0 after flushing seek
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Thu Jun 11 02:06:59 PDT 2015
https://bugzilla.gnome.org/show_bug.cgi?id=750027
Sebastian Dröge (slomo) <slomo at coaxion.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
Hrm, forgot to ammend your commit before pushing. Please don't put the
"Signed-off-by" noise into commit messages, and instead put a link to the bug
report there :) git-bz does that automatically for you.
commit d8db88d078dc2688858ec6393379ade6b5990771
Author: Sebastian Dröge <sebastian at centricular.com>
Date: Thu Jun 11 11:05:53 2015 +0200
concat: Also reset the current start offset when receiving a FLUSH_STOP on
the srcpad
commit c324e31c26e7eb088ac79001e4eb5ed76fe8f094
Author: Sebastian Dröge <sebastian at centricular.com>
Date: Thu Jun 11 11:05:38 2015 +0200
concat: Add some newlines to event handling code to make the code look a
bit less dense
commit 25c66e60045e44d50a591f5d62706f6f243bb9ca
Author: Carlos Rafael Giani <dv at pseudoterminal.org>
Date: Thu Jun 11 10:53:30 2015 +0200
concat: Reset segment base offset after FLUSH_STOP with reset_time = TRUE
If the reset_time value of a FLUSH_STOP event is set to TRUE, the pipeline
will have the base_time of its elements reset. This means that the concat
element's current_start_offset has to be reset to 0, since it was
calculated with the old base-time in mind.
Only FLUSH_STOP events coming from the active pad are looked at.
Signed-off-by: Carlos Rafael Giani <dv at pseudoterminal.org>
--
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