Merge branch 'master' into release-2.1

docs/clients/mpd.rst

@@ -75,6 +75,14 @@ than with a normal MPD server, which has a local cache of meta data. Thus, GMPC
 may sometimes feel frozen, but usually you just need to give it a bit of slack
 before it will catch up.
 
+MPDel
+-----
+
+`MPDel <https://gitlab.petton.fr/mpdel/mpdel>`_ is an MPD client working within `Emacs <https://www.gnu.org/software/emacs/>`_.
+
+.. image:: mpd-client-mpdel.png
+    :width: 649
+    :height: 438
 
 Sonata
 ------
@@ -162,7 +170,7 @@ Rompr
     :width: 557
     :height: 600
 
-`Rompr <http://sourceforge.net/projects/rompr/>`_ is a web based MPD client.
+`Rompr <https://fatg3erman.github.io/RompR/>`_ is a web based MPD client.
 `mrvanes <https://github.com/mrvanes>`_, a Mopidy and Rompr user, said: "These
 projects are a real match made in heaven."
 

docs/clients/mpris.rst

@@ -48,10 +48,9 @@ Under normal use, if Mopidy isn't running and you open the menu and click on
 Mopidy. If Mopidy is already running, you'll see that Mopidy is marked with an
 arrow to the left of its name, like in the screen shot above, and the player
 controls will be visible. Mopidy doesn't support the MPRIS spec's optional
-playlist interface yet, so you'll not be able to select what track to play from
-the sound menu. If you use an MPD client to queue a playlist, you can use the
-sound menu to check what you're currently playing, pause, resume, and skip to
-the next and previous track.
+tracklist interface yet, so you'll not be able to select what track to play
+from the sound menu. You can use the sound menu to check what you're currently
+playing, pause, resume, and skip to the next and previous track.
 
 In summary, Mopidy's sound menu integration is currently not a full featured
 client, but it's a convenient addition to an MPD client since it's always

docs/ext/frontends.rst

@@ -41,14 +41,6 @@ Extension for controlling Mopidy through the `MPRIS <http://www.mpris.org/>`_
 D-Bus interface, for example using the Ubuntu Sound Menu.
 
 
-Mopidy-Notifier
-===============
-
-https://github.com/sauberfred/mopidy-notifier
-
-Extension for displaying track info as User Notifications in Mac OS X.
-
-
 Mopidy-Scrobbler
 ================
 

docs/extensiondev.rst

@@ -586,7 +586,7 @@ Test cases for checking the definition of the extension should ensure that:
 
 An example of what these tests could look like is provided below::
 
-    def test_get_default_config(self):
+    def test_get_default_config():
         ext = Extension()
         config = ext.get_default_config()
 
@@ -596,7 +596,7 @@ An example of what these tests could look like is provided below::
         assert 'param_2 = value_2' in config
         assert 'param_n = value_n' in config
 
-    def test_get_config_schema(self):
+    def test_get_config_schema():
         ext = Extension()
         schema = ext.get_config_schema()
 
@@ -605,7 +605,7 @@ An example of what these tests could look like is provided below::
         assert 'param_2' in schema
         assert 'param_n' in schema
 
-    def test_setup(self):
+    def test_setup():
         registry = mock.Mock()
 
         ext = Extension()
@@ -783,4 +783,4 @@ the events fire::
 
 For further details and examples, refer to the
 `/tests <https://github.com/mopidy/mopidy/tree/develop/tests>`_
-directory on the Mopidy development branch.
+directory on the Mopidy development branch.

docs/installation/debian.rst

@@ -16,11 +16,11 @@ from scratch, we have a guide for installing Debian/Raspbian and Mopidy. See
 
 The packages are built for:
 
-- Debian jessie (stable), which also works for Raspbian jessie and Ubuntu 14.04
-  LTS and newer.
+- Debian stretch (stable), which also works for Raspbian stretch and Ubuntu
+  16.04 LTS and newer.
 
 The packages are available for multiple CPU architectures: i386, amd64, armel,
-and armhf (compatible with Raspberry Pi 1 and 2).
+and armhf (compatible with all Raspberry Pi models).
 
 .. note::
 
@@ -35,16 +35,17 @@ and armhf (compatible with Raspberry Pi 1 and 2).
 
 #. Add the APT repo to your package sources::
 
-       sudo wget -q -O /etc/apt/sources.list.d/mopidy.list https://apt.mopidy.com/jessie.list
+       sudo wget -q -O /etc/apt/sources.list.d/mopidy.list https://apt.mopidy.com/stretch.list
 
 #. Install Mopidy and all dependencies::
 
        sudo apt-get update
        sudo apt-get install mopidy
 
-#. Finally, you need to set a couple of :doc:`config values </config>`, and then
-   you're ready to :doc:`run Mopidy </running>` or run Mopidy as a
-   :ref:`service <service>`.
+#. Finally, you need to set a couple of :doc:`config values </config>`, and
+   then you're ready to :doc:`run Mopidy </running>`. Alternatively you may
+   want to have Mopidy run as a :ref:`system service <service>`, automatically
+   starting at boot.
 
 When a new release of Mopidy is out, and you can't wait for you system to
 figure it out for itself, run the following to upgrade right away::

docs/installation/raspberrypi.rst

@@ -5,23 +5,23 @@ Raspberry Pi
 ************
 
 Mopidy runs on all versions of `Raspberry Pi <https://www.raspberrypi.org/>`_.
-However, note that Raspberry Pi 2 B's CPU is approximately six times as
-powerful as Raspberry Pi 1 and Raspberry Pi Zero, so Mopidy will be more joyful
-to use on a Raspberry Pi 2.
+However, note that the Raspberry Pi 2 and 3 are significantly more powerful than
+the Raspberry Pi 1 and Raspberry Pi Zero; Mopidy will run noticably faster on
+the later models.
 
 .. image:: raspberrypi2.jpg
     :width: 640
     :height: 363
 
 
-How to for Raspbian Jessie
-==========================
+How to for Raspbian
+===================
 
-#. Download the latest Jessie or Jessie Lite disk image from
+#. Download the latest Raspbian Desktop or Lite disk image from
    http://www.raspberrypi.org/downloads/raspbian/.
 
-   If you're only using your Pi for Mopidy, go with Jessie Lite as you won't
-   need the full graphical desktop included in the Jessie image.
+   Unless you need a full graphical desktop the Lite image is preferable since
+   it's much smaller.
 
 #. Flash the Raspbian image you downloaded to your SD card.
 
@@ -32,12 +32,11 @@ How to for Raspbian Jessie
    You'll need to enable SSH if you are not connecting a monitor and a keyboard.
    As of the November 2016 release, Raspbian has the SSH server disabled by
    default. SSH can be enabled by placing a file named 'ssh', without any
-   extension, onto the boot partition of the SD card.
+   extension, onto the boot partition of the SD card. See `here
+   <https://www.raspberrypi.org/documentation/remote-access/ssh/README.md>`_ for
+   more details.
 
-#. If you connect a monitor and a keyboard, you'll see that the Pi boots right
-   into the ``raspi-config`` tool.
-
-   If you boot with only a network cable connected, you'll have to find the IP
+#. If you boot with only a network cable connected, you'll have to find the IP
    address of the Pi yourself, e.g. by looking in the client list on your
    router/DHCP server. When you have found the Pi's IP address, you can SSH to
    the IP address and login with the user ``pi`` and password ``raspberry``.
@@ -47,32 +46,37 @@ How to for Raspbian Jessie
 #. Use the ``raspi-config`` tool to setup the basics of your Pi. You might want
    to do one or more of the following:
 
-   - Expand the file system to fill the SD card.
    - Change the password of the ``pi`` user.
-   - Change the time zone.
+   - Change the language, time zone, etc.
 
    Under "Advanced Options":
 
    - Set a hostname.
    - Enable SSH if not already enabled.
-   - If your will use HDMI for display and 3.5mm jack for audio, force the
-     audio output to the 3.5mm jack. By default it will use HDMI for audio
-     output if an HDMI cable is connected and the 3.5mm jack if not.
+   - Force a specific audio output.
+     By default, when using a HDMI display the
+     audio will also be output over HDMI, otherwise the 3.5mm jack will be used.
+   - Adjust the memory split.
+     If you're not using a display (i.e. Raspbian
+     Lite), you should set the minimum value here in order to make best use of
+     the available RAM.
 
-   Once done, select "Finish" and restart your Pi.
+   Once done, select "Finish". Depending on what you changed you may be asked if
+   you want to restart your Pi, select "Yes" and then log back in again
+   afterwards.
 
    If you want to change any settings later, you can simply rerun ``sudo
    raspi-config``.
 
-#. Once you've rebooted and has logged in as the ``pi`` user, you can enter
-   ``sudo -i`` to become ``root``.
 
-#. Install Mopidy and its dependencies as described in :ref:`debian-install`.
+#. Install Mopidy and any Mopidy extensions you want, as described in
+   :ref:`debian-install`.
 
-#. Finally, you need to set a couple of :doc:`config values </config>`, and
-   then you're ready to :doc:`run Mopidy </running>`. Alternatively you may
-   want to have Mopidy run as a :ref:`system service <service>`, automatically
-   starting at boot.
+.. note::
+
+   If you used the Raspbian *Desktop* image you may also need to add the
+   ``mopidy`` user to the ``video`` group. Run ``sudo adduser mopidy video``
+   to do this.
 
 
 Testing sound output
@@ -84,10 +88,5 @@ You can test sound output independent of Mopidy by running::
 
 If you hear a voice saying "Front Center", then your sound is working.
 
-If you want to change your audio output setting, simply rerun ``sudo
-raspi-config``. Alternatively, you can change the audio output setting
-directly by running:
-
-- Auto (HDMI if connected, else 3.5mm jack): ``sudo amixer cset numid=3 0``
-- Use 3.5mm jack: ``sudo amixer cset numid=3 1``
-- Use HDMI: ``sudo amixer cset numid=3 2``
+If you want to change your audio output setting, simply rerun ``sudo 
+raspi-config``.