[gstreamer-bugs] [Bug 483923] New: audio pipeline cannot change its state to "PLAYING"

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=483923

  GStreamer | gst-plugins-good | Ver: 0.10.14
           Summary: audio pipeline cannot change its state to "PLAYING"
           Product: GStreamer
           Version: 0.10.14
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: blocker
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: bohan.gnome at retropaganda.info
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
I made a pipeline that connects an audiotestsrc to a gconfaudiosink (which is
audioconvert ! audioresample ! esdsink).
The pipeline is requested to change its state to PLAYING.
The pipeline stays in state PAUSED forever.


Steps to reproduce:
sample program attached

Actual results:
The pipeline stays in state PAUSED forever.

Expected results:
I was expecting the pipeline to eventually change its state to PLAYING.

Does this happen every time?
yes

Other information:
The gstreamer sample program is run on linux, and the esdsink is connected via
network to a remote cygwin esound daemon version 0.2.36.

The "Test" button in the "Default output" of the gstreamer-properties app is
working fine.

The sample program emits sound despite the pipeline being in PAUSED state.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=483923.