After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 122279 - goom's first timestamp is broken
goom's first timestamp is broken
Status: VERIFIED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal major
: 0.7.6
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-09-14 16:45 UTC by Julien MOUTTE
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
dirty patch from ronald (4.44 KB, patch)
2003-09-16 17:13 UTC, Julien MOUTTE 		none Details | Review

Description Julien MOUTTE 2003-09-14 16:45:37 UTC 
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
output will have heavily broken timestamps.

bug is in 0.6.x too and needs to be fixed there, too.
Comment 1 Julien MOUTTE 2003-09-16 17:13:34 UTC 
Created attachment 19991 [details] [review]
dirty patch from ronald
Comment 2 David Schleef 2004-03-06 03:10:25 UTC 
Uh, this is a patch for gsttee.c.
Comment 3 David Schleef 2004-03-06 03:19:16 UTC 
This appears to be fixed in HEAD.  That is, goom ! ffcolorspace !
timeoverlay ! xvimagesink has the correct timestamp even when
linking/unlinking in gst-editor.
Comment 4 Ronald Bultje 2004-03-06 07:55:03 UTC 
That's not hard. The issue is when you're tee'ing it.

                          goom -> videosink
filesrc -> ... -> tee -> 
                          osssink

Then, if you connect tee<->goom halfway, it hangs.
Comment 5 David Schleef 2004-03-07 19:01:55 UTC 
No, really.  It works.
Comment 6 Christian Fredrik Kalager Schaller 2004-11-25 18:04:42 UTC 
Jan went through and fixed all the visualizations so I am closing this old bug
as fixed.