andpp/mopidy
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs: Remove GStreamer elements from extdev guide

Browse Source 
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.
This commit is contained in:
Stein Magnus Jodal 2015-03-14 20:59:49 +01:00
parent 0eb2e1675a
commit 3dc1901436
1 changed files with 0 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/extensiondev.rst
View File

@ -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
====================