After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 705976 - per-pipeline element factory modifier ranks
per-pipeline element factory modifier ranks
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-08-14 10:20 UTC by Tim-Philipp Müller
Modified: 2018-11-03 12:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tim-Philipp Müller 2013-08-14 10:20:07 UTC
Imagine a library that internally uses GStreamer's playbin to provide certain functionality, like libwebkitgtk perhaps. Imagine that library needs to make playbin pick a custom http source. It will have to register a custom source that has a higher rank than e.g. souphttpsrc.

Now imagine the application also wants to do something with playbin. Now the application playbin will inadvertently also use the webkit http source, which may or may not work.

One could solve this by either providing modifier ranks on a per-pipeline basis, or adding API to playbin/uridecodebin etc. that lets users override the source selection.
Comment 1 Stefan Sauer (gstreamer, gtkdoc dev) 2014-02-01 21:08:36 UTC
Couldn't the app call gst_plugin_feature_set_rank() to bump the rank for selected features?
Comment 2 Tim-Philipp Müller 2014-02-02 11:22:16 UTC
> Couldn't the app call gst_plugin_feature_set_rank() to bump the rank for
> selected features?

It could, but that would change the rank globally not per pipeline, which does not help with the problem described.
Comment 3 GStreamer system administrator 2018-11-03 12:18:37 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/41.