[gst-devel] gst_pipeline_new and GObject-y bits

Benjamin Otte in7y118 at public.uni-hamburg.de
Tue Apr 6 08:13:27 CEST 2004

On Tue, 6 Apr 2004, Thomas Vander Stichele wrote:

> On Sat, 2004-04-03 at 16:51, Benjamin Otte wrote:
> > The simple, elegant and best solution is of course to check for
> > scheduler availablibity (at least the default scheduler) in gst_init.
> > Solves all your problems.
> I don't think it does - there's more than one scheduler, we want to move
> on to supporting more than one scheduler in a pipeline too, and the
> default scheduler can be changed after _init as well.  It was my first
> idea too, but it's a hack.
No, there's only one default scheduler and that scheduler is defined at
system initialization time by GStreamer.
It should definitely be possible to change it for an app. If an app wants
a different scheduler, it should set that one on the managers it creates.
The reason for this is simple, too: Changing the default scheduler changes
behaviour of everything related to gst. You don't know what parts of your
app use GStreamer. Just imagine you setting the scheduler in an app of
yours and then gdk-pixbuf crashes because of the gst-gdk-pixbuf loader.


More information about the gstreamer-devel mailing list