[Gstreamer-bugs] [Bug 122279] Changed - goom's first timestamp is broken
bugzilla-daemon at widget.gnome.org
bugzilla-daemon at widget.gnome.org
Fri Mar 5 19:19:17 PST 2004
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugzilla.gnome.org/show_bug.cgi?id=122279
Changed by ds at schleef.org.
--- shadow/122279 Fri Mar 5 22:10:26 2004
+++ shadow/122279.tmp.19770 Fri Mar 5 22:19:17 2004
@@ -1,20 +1,20 @@
Bug#: 122279
Product: GStreamer
Version: HEAD CVS
OS: Linux
OS Details:
-Status: NEW
-Resolution:
+Status: RESOLVED
+Resolution: FIXED
Severity: major
Priority: Normal
Component: gst-plugins
AssignedTo: gstreamer-maint at bugzilla.gnome.org
ReportedBy: julien at moutte.net
QAContact: gstreamer-maint at bugzilla.gnome.org
-TargetMilestone: HEAD
+TargetMilestone: 0.7.6
URL:
Summary: goom's first timestamp is broken
goom does not check the timestamp of its input. if the first timestamp !=
0, goom does not set the output's first buffer timestamps to this number.
The result is that if you connect a running pipeline to goom, the goom
@@ -26,6 +26,11 @@
Created an attachment (id=19991)
dirty patch from ronald
------- Additional Comments From ds at schleef.org 2004-03-05 22:10 -------
Uh, this is a patch for gsttee.c.
+
+------- Additional Comments From ds at schleef.org 2004-03-05 22:19 -------
+This appears to be fixed in HEAD. That is, goom ! ffcolorspace !
+timeoverlay ! xvimagesink has the correct timestamp even when
+linking/unlinking in gst-editor.
More information about the Gstreamer-bugs
mailing list