[gstreamer-bugs] [Bug 620277] New: [pulsesink] custom clock is still used after NULL state change

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=620277
  GStreamer | gst-plugins-good | git

           Summary: [pulsesink] custom clock is still used after NULL
                    state change
    Classification: Desktop
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: gst-plugins-good
        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)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=162473)
Very simple test script

This commit introduced a major regression:

http://cgit.freedesktop.org/gstreamer/gst-plugins-good/commit/?id=e69ba0f94f475975cfa33d651a56fc1567c0238b

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
playbin2.

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.