[Gstreamer-bugs] [Bug 114976] Changed - [0.6.3/patch] videotestsrc and xvideosink do not reset their state when going to NULL
bugzilla-daemon at widget.gnome.org
bugzilla-daemon at widget.gnome.org
Thu Aug 21 17:43:48 PDT 2003
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=114976
Changed by ds at schleef.org.
--- shadow/114976 Thu Aug 21 05:25:26 2003
+++ shadow/114976.tmp.8673 Thu Aug 21 20:43:48 2003
@@ -45,6 +45,23 @@
------- Additional Comments From thomas at urgent.rug.ac.be 2003-08-21 05:25 -------
why shouldn't element data be reset even from READY to NULL ?
AFAIK, all plugins going to NULL should behave as if they were freshly
created, why is this not the case ?
+
+------- Additional Comments From ds at schleef.org 2003-08-21 20:43 -------
+> why shouldn't element data be reset even from READY to NULL ?
+
+Element data, yes. But (writable) parameters should (ideally) never
+be changed except under the control of the application.
+
+Reseting parameters to the default in READY->NULL makes it much more
+difficult for elements to use the NULL state to free their resources.
+ A good example is osssink -- I don't think that it's a good idea to
+reset the device parameter every time we want osssink to detach from
+the device (i.e., every time the user presses pause on a GUI).
+
+If an application wants a pristine element, it can create one. I
+don't see a good reason to support restoring elements to a pristine
+state. One could probably approximate it by going through all the
+parameters and calling g_param_value_set_default(), though.
More information about the Gstreamer-bugs
mailing list