Glossary
- backend
- A part of Mopidy providing music library, playlist storage and/or
playback capability to the core. Mopidy has a backend for each
music store or music service it supports. See mopidy.backend — Backend API for
details.
- core
- The part of Mopidy that makes multiple frontends capable of using
multiple backends. The core module is also the owner of the
tracklist. To use the core module, see mopidy.core — Core API.
- extension
- A Python package that can extend Mopidy with one or more
backends, frontends, or GStreamer
elements like mixers. See Extensions for a list of
existing extensions and Extension development for how to make a new
extension.
- frontend
- A part of Mopidy using the core API. Existing frontends
include the MPD server, the MPRIS/D-Bus integration,
the Last.fm scrobbler, and the HTTP server with
JavaScript API. See Frontend API for details.
- mixer
- A GStreamer element that controls audio volume.
- tracklist
- Mopidy’s name for the play queue or current playlist. The name is
inspired by the MPRIS specification.