[Gstreamer-bugs] [Bug 114331] Changed - scheduler should not schedule PAUSED elements

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=114331

Changed by in7y118 at public.uni-hamburg.de.

--- shadow/114331	Tue Jun  3 07:03:37 2003
+++ shadow/114331.tmp.22771	Tue Jun  3 07:08:34 2003
@@ -11,13 +11,12 @@
 AssignedTo: gstreamer-maint at bugzilla.gnome.org                            
 ReportedBy: julien at moutte.net               
 QAContact: gstreamer-maint at bugzilla.gnome.org
 TargetMilestone: 0.6.x
 URL: 
 Summary: scheduler should not schedule PAUSED elements
-OtherBugsDependingOnThis: 111362
 
 It seems that scheduler is scheduling element that are in PAUSED state..
 
 For example if you try to play an audio file while xmms is playing through
 oss at the same time. You will receive thousands of "error" signal from
 pipeline with error message "osscommon: Unable to open /dev/dsp (in use ?)"
@@ -25,6 +24,23 @@
 osssink was not able to switch to READY but it gets scheduled and i m
 flooded by error messages.
 
 Benjamin thinks it's a scheduler issue..
 
 We would need to fix that for 0.6.2 !
+
+------- Additional Comments From in7y118 at public.uni-hamburg.de  2003-06-03 07:08 -------
+There is another issue with this that is quite fundamental:
+
+Some plugins seek back if they receive an EOS (bug 111498 is an
+example of this - maybe two-pass encoding, too?)
+An EOS makes plugins go to PAUSED however so they might not be
+scheduled after that.
+To fix that I can imagine 2 possibilities:
+- Create a new state GST_STATE_EOS (ugly but makes sense, plugins
+might behave differently when going to EOS than when going to PAUSED -
+alsa for example drains the audio buffer and stops on EOS while it
+immediately pauses when going to PAUSED, i had to special case there)
+This is my preferred idea
+- Allow plugins to set themselves to PLAYING when receiving events.
+This is ugly somehow because state changes are something explicit and
+shouldn't be triggered by weird stuff like seek events.