[gstreamer-bugs] [Bug 585268] fakesink doesn't go to playing with a wav file

[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=585268

  GStreamer | gstreamer (core) | Ver: 0.10.23

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |t.i.m at zen.co.uk
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1




------- Comment #7 from Tim-Philipp Müller  2009-06-15 19:45 UTC -------
There is something quite wrong here indeed.

For example: it seems that when it fails to transition from PAUSED->PLAYING,
_set_state() returns ASYNC, whereas it should return SUCCESS.

The EOS failure case would imply that a state-change message got 'lost'
somewhere, or there's a race going on where the EOS is posted before the
PAUSED->PLAYING state change message. The log points towards the latter:

0:00:00.302314478 29153       0xec1160 gst_bus_post:<bus7> [msg 0xecc6c0]
posting on bus, type new-clock, GstMessageNewClock,
clock=(GstClock)"\(GstSystemClock\)\ GstSystemClock"; from source <playbin>
0:00:00.308706073 29153      0x10a4640 gst_bus_post:<bus7> [msg 0x10ab710]
posting on bus, type eos, (NULL) from source <playbin>
0:00:00.308916574 29153       0xec1160 gst_bus_post:<bus7> [msg 0xf52660]
posting on bus, type state-changed, GstMessageState,
old-state=(GstState)GST_STATE_PAUSED, new-state=(GstState)GST_STATE_PLAYING,
pending-state=(GstState)GST_STATE_VOID_PENDING; from source <playbin>


-- 
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=585268.