[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: git




------- Comment #14 from Wim Taymans  2009-06-16 16:29 UTC -------
(In reply to comment #12)
> (In reply to comment #11)
> > > The EOS before the state-change message can happen and is not considered to be
> > > an error. Do you think we should make it so that the state change is before the
> > > EOS? (this is not so trivial to do)..
> 
> Problem is that we are using fakesink to mock playback in some tests and in
> this case, I guess it should never happen that you get EOS before playing
> anything.

The reason is that the EOS message is posted by the sink and passed through to
the application while the state change message of the pipeline is posted after
all elements in the pipeline performed the state change. 

In this example application, the sink is set to PLAYING first, races to EOS and
posts EOS before the pipeline managed to change the state of the other elements
and before it managed to post the state change message to PLAYING. 

One possible solution would be to queue the EOS messages from the sinks and
only post them when the pipeline reached PLAYING, after it posted the state
change message. This would be the right thing to do, indeed.

> 
> > Hrm, I think so. I find this highly unexpected at least. The order of the async
> > messages should reflect the underlying design rules IMHO (ie. here: eos can
> > only happen in playing state).
> 
> Actually, I guess it could if you just seek to the end, but it is not this
> case.
> 


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