From 3dc19014367a08427a2454eaf3b2ce1f8a1c92e2 Mon Sep 17 00:00:00 2001 From: Stein Magnus Jodal Date: Sat, 14 Mar 2015 20:59:49 +0100 Subject: [PATCH] docs: Remove GStreamer elements from extdev guide Mixers are no longer custom GStreamer elements, and while still possible to do, custom GStreamer elements will probably not be as well supported when we port to GStreamer 1.x. --- docs/extensiondev.rst | 17 ----------------- 1 file changed, 17 deletions(-) diff --git a/docs/extensiondev.rst b/docs/extensiondev.rst index 93f627dc..a2a5f463 100644 --- a/docs/extensiondev.rst +++ b/docs/extensiondev.rst @@ -307,12 +307,6 @@ This is ``mopidy_soundspot/__init__.py``:: from .backend import SoundspotBackend registry.add('backend', SoundspotBackend) - # Register a custom GStreamer element - from .mixer import SoundspotMixer - gobject.type_register(SoundspotMixer) - gst.element_register( - SoundspotMixer, 'soundspotmixer', gst.RANK_MARGINAL) - # Or nothing to register e.g. command extension pass @@ -416,17 +410,6 @@ examples, see the :ref:`http-server-api` docs or explore with :ref:`http-explore-extension` extension. -Example GStreamer element -========================= - -If you want to extend Mopidy's GStreamer pipeline with new custom GStreamer -elements, you'll need to register them in GStreamer before they can be used. - -Basically, you just implement your GStreamer element in Python and then make -your :meth:`~mopidy.ext.Extension.setup` method register all your custom -GStreamer elements. - - Running an extension ====================