Mopidy¶
Mopidy is an extensible music server written in Python.
Mopidy plays music from local disk, Spotify, SoundCloud, Google Play Music, and more. You edit the playlist from any phone, tablet, or computer using a range of MPD and web clients.
Stream music from the cloud
Vanilla Mopidy only plays music from your local disk and radio streams. Through extensions, Mopidy can play music from cloud services like Spotify, SoundCloud, and Google Play Music. With Mopidy’s extension support, backends for new music sources can be easily added.
Mopidy is just a server
Mopidy is a Python application that runs in a terminal or in the background on Linux computers or Macs that have network connectivity and audio output. Out of the box, Mopidy is an MPD and HTTP server. Additional frontends for controlling Mopidy can be installed from extensions.
Everybody use their favorite client
You and the people around you can all connect their favorite MPD or web client to the Mopidy server to search for music and manage the playlist together. With a browser or MPD client, which is available for all popular operating systems, you can control the music from any phone, tablet, or computer.
Mopidy on Raspberry Pi
The Raspberry Pi is a popular device to run Mopidy on, either using Raspbian or Arch Linux. It is quite slow, but it is very affordable. In fact, the Kickstarter funded Gramofon: Modern Cloud Jukebox project used Mopidy on a Raspberry Pi to prototype the Gramofon device. Mopidy is also a major building block in the Pi Musicbox integrated audio jukebox system for Raspberry Pi.
Mopidy is hackable
Mopidy’s extension support and Python, JSON-RPC, and JavaScript APIs makes Mopidy perfect for building your own hacks. In one project, a Raspberry Pi was embedded in an old cassette player. The buttons and volume control are wired up with GPIO on the Raspberry Pi, and is used to control playback through a custom Mopidy extension. The cassettes have NFC tags used to select playlists from Spotify.
Getting started
To get started with Mopidy, start by reading Installation.
Getting help
If you get stuck, you can get help at the our Discourse forum or in the #mopidy-users
stream on Zulip
chat.
If you stumble into a bug or have a feature request, please create an issue in the issue tracker. If you’re unsure if it’s a bug or not, ask for help in the forum or the chat first. The source code may also be of help.
If you want to stay up to date on Mopidy developments, you can follow the
#mopidy-dev
stream on Zulip chat or
watch out for announcements on the Discourse forum.
Usage
Extensions¶
- Mopidy-Local
- Mopidy-File
- Mopidy-M3U
- Mopidy-Stream
- Mopidy-HTTP
- Mopidy-MPD
- Mopidy-SoftwareMixer
- Mixer extensions
- Backend extensions
- Mopidy-AudioAddict
- Mopidy-Banshee
- Mopidy-Bassdrive
- Mopidy-Beets
- Mopidy-Dirble
- Mopidy-dLeyna
- Mopidy-Emby
- Mopidy-File
- Mopidy-GMusic
- Mopidy-InternetArchive
- Mopidy-Local
- Mopidy-Local-Images
- Mopidy-Local-SQLite
- Mopidy-OE1
- Mopidy-Podcast
- Mopidy-Podcast-gpodder
- Mopidy-Podcast-iTunes
- Mopidy-radio-de
- Mopidy-RNZ
- Mopidy-SomaFM
- Mopidy-SoundCloud
- Mopidy-Spotify
- Mopidy-Spotify-Tunigo
- Mopidy-Stream
- Mopidy-Subsonic
- Mopidy-TuneIn
- Mopidy-VKontakte
- Mopidy-YDisk
- Mopidy-YouTube
- Frontend extensions
- Web extensions
Clients
Development
- Contributing
- Development environment
- Release procedures
- Code style
- Extension development
- Anatomy of an extension
- cookiecutter project template
- Example README.rst
- Example setup.py
- Example __init__.py
- Example frontend
- Example backend
- Example command
- Example web application
- Running an extension
- Python conventions
- Use of Mopidy APIs
- Logging in extensions
- Making HTTP requests from extensions
- Testing extensions
Reference