[gstreamer-bugs] [Bug 620277] New: [pulsesink] custom clock is still used after NULL state change
bugzilla at gnome.org
Tue Jun 1 09:51:18 PDT 2010
GStreamer | gst-plugins-good | git
Summary: [pulsesink] custom clock is still used after NULL
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: mail at renestadler.de
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME target: ---
GNOME version: ---
Created an attachment (id=162473)
Very simple test script
This commit introduced a major regression:
If you apply it, reusing pulsesink is mostly broken. As in the simple test
script attached, a pipeline like audiotestsrc ! pulsesink will produce broken
audio output after a NULL->PLAYING->NULL->PLAYING transition. This also affects
The problem is that there is nothing producing a clock-lost message. This leads
the gstbin class to keeping the old clock around. Not sure if the fix is as
simple as firing clock-lost in pulsesink READY->NULL though.
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