Changelog 2.x series¶
This is the changelog of Mopidy v2.0.0 through v2.3.1.
For the latest releases, see Changelog.
Bug fix release.
Dependencies: Lower requirement for Tornado from
>= 5, < 6to
>= 4.4, < 6. Our HTTP server implementation works with Tornado 4 as well, which is the latest version that is packaged on Ubuntu 18.04 LTS.
Mopidy 2.3.0 is mostly a bug fix release. Because we’re requiring a new major version of Tornado, we’re doing a minor version bump of Mopidy.
Bug fix release.
.zipto the default
local/excluded_file_extensionsconfig value. (PR: #1737)
Docs: Resize and compress images, reducing the release tarball size from 3.5 to 1.1 MB.
Docs: Fix broken links.
Bug fix release.
Bug fix release.
HTTP: Add new config value
http/csrf_protectionwhich enables all CSRF protections introduced in Mopidy 2.2.0. It is enabled by default and should only be disabled by those users who are unable to set a
Content-Type: application/jsonrequest header or cannot utilise the
http/allowed_originsconfig value. (Fixes: #1713, PR: #1714)
Mopidy 2.2.0, a feature release, is out. It is a quite small release, featuring mostly minor fixes and improvements.
Most notably, this release introduces CSRF protection for both the HTTP and WebSocket RPC interfaces, and improves the file path checking in the M3U backend. The CSRF protection should stop attacks against local Mopidy servers from malicious websites, like what was demonstrated by Josef Gajdusek in #1659.
Since the release of 2.1.0, we’ve closed approximately 21 issues and pull requests through 133 commits by 22 authors.
Dependencies: Drop support for Tornado < 4.4. Though strictly a breaking change, this shouldn’t affect any supported systems as even Debian stable includes Tornado >= 4.4.
Core: Remove upper limit of 10000 tracks in tracklist. 10000 tracks is still the default limit as some MPD clients crash if the tracklist is longer, but it is now possible to set the
core/max_tracklist_lengthconfig value as high as you want to. (Fixes: #1600, PR: #1666)
Core: Define return value of
playlists.delete()to be a bool,
Falseotherwise. (PR: #1702)
File: Change default ordering to show directories first, then files. (PR: #1595)
File: Fix extraneous encoding of path. (PR: #1611)
HTTP: Protect RPC and WebSocket interfaces against CSRF by blocking requests that originate from servers other than those specified in the new config value
http/allowed_origins. An artifact of this is that all JSON-RPC requests must now always set the header
Content-Type: application/json. (Partly fixes: #1659, PR: #1668)
Ensure that decoding of OS errors with unknown encoding never crashes, but instead replaces unknown bytes with a replacement marker. (Fixes: #1599)
Set GLib program and application name, so that we show up as “Mopidy” in PulseAudio instead of “python …”. (PR: #1626)
Mopidy 2.1.0, a feature release, is finally out!
Since the release of 2.0.0, it has been quiet times in Mopidy circles. This is mainly caused by core developers moving from the enterprise to startups or into positions with more responsibility, and getting more kids. Of course, this has greatly decreased the amount of spare time available for open source work. But fear not, Mopidy is not dead. We’ve returned from year long periods with close to no activity before, and will hopefully do so again.
Despite all, we’ve closed or merged approximately 18 issues and pull requests through about 170 commits since the release of v2.0.1 back in August.
The major new feature in Mopidy 2.1 is support for restoring playback state and the current playlist after a restart. This feature was contributed by Jens Lütjen.
Dependencies: Drop support for Tornado < 3.2. Though strictly a breaking change, this shouldn’t have any effect on what systems we support, as Tornado 3.2 or newer is available from the distros that include GStreamer >= 1.2.3, which we already require.
Core: Mopidy restores its last state when started. Can be enabled by setting the config value
Audio: Update scanner to handle sources such as RTSP. (Fixes: #1479)
File: Add new config value
MPD: Fix MPD protocol for
replay_gain_statuscommand. The actual command remains unimplemented. (PR: #1520)
Bug fix release.
soft-volumeflag on GStreamer’s playbin element. This is the playbin’s default, but we managed to override it when configuring the playbin to only process audio. This should fix the “Volume/mute is not available” warning.
Audio: Make sure scanner handles streams without a duration. (Fixes: #1526)
Audio: Ensure audio tags are never
None. (Fixes: #1449)
Mopidy 2.0 is here!
Since the release of 1.1, we’ve closed or merged approximately 80 issues and pull requests through about 350 commits by 14 extraordinary people, including 10 newcomers. That’s about the same amount of issues and commits as between 1.0 and 1.1. The number of contributors is a bit lower but we didn’t have a real life sprint during this development cycle. Thanks to everyone who has contributed!
With the release of Mopidy 1.0 we promised that any extension working with Mopidy 1.0 should continue working with all Mopidy 1.x releases. Mopidy 2.0 is quite a friendly major release and will only break a single extension that we know of: Mopidy-Spotify. To ensure that everything continues working, please upgrade to Mopidy 2.0 and Mopidy-Spotify 3.0 at the same time.
No deprecated functionality has been removed in Mopidy 2.0.
The major features of Mopidy 2.0 are:
Gapless playback has been mostly implemented. It works as long as you don’t change tracks in the middle of a track or use previous and next. In a future release, previous and next will also become gapless. It is now quite easy to have Mopidy streaming audio over the network using Icecast. See the updated Icecast docs for details of how to set it up and workarounds for the remaining issues.
Mopidy has upgraded from GStreamer 0.10 to 1.x. This has been in our backlog for more than three years. With this upgrade we’re ridding ourselves of years of GStreamer bugs that have been fixed in newer releases, we can get into Debian testing again, and we’ve removed the last major roadblock for running Mopidy on Python 3.
Mopidy now requires GStreamer >= 1.2.3, as we’ve finally ported from GStreamer 0.10. Since we’re requiring a new major version of our major dependency, we’re upping the major version of Mopidy too. (Fixes: #225)
tlidcounting at 1 instead of 0 to keep in sync with MPD’s
Log exception and continue if an extension crashes during setup. Previously, we let Mopidy crash if an extension’s setup crashed. (PR: #1337)
local/data_dirreally deprecated. This change breaks older versions of Mopidy-Local-SQLite and Mopidy-Local-Images.
No longer scan playlist directory and parse playlists at startup or refresh. Similarly tothe file extension, this now happens on request.
mopidy.models.Refinstances when reading and writing playlists. Therefore,
Track.lengthis no longer stored in extended M3U playlists and
#EXTINFruntime is always set to -1.
Improve reliability of playlist updates using the core playlist API by applying the write-replace pattern for file updates.
Implemented commands for modifying stored playlists:
songidcounting at 1 instead of 0 to match the original MPD server.
Event handler for
playlist_deletedhas been unbroken. This unreported bug would cause the MPD frontend to crash preventing any further communication via the MPD protocol. (PR: #1347)
Removed warning if
~/.mopidyexists. We stopped using this location in 0.6, released in October 2011.
Removed warning if
~/.config/mopidy/settings.pyexists. We stopped using this settings file in 0.14, released in April 2013.
on_eventhandler in our listener helper now catches exceptions. This means that any errors in event handling won’t crash the actor in question.
Breaking: Removed unused internal
mopidy.internal.process.BaseThread. This breaks Mopidy-Spotify 1.4.0. Versions < 1.4.0 was already broken by Mopidy 1.1, while versions >= 2.0 doesn’t use this class.
Breaking: The audio scanner now returns ISO-8601 formatted strings instead of
datetimeobjects for dates found in tags. Because of this change, we can now return years without months or days, which matches the semantics of the date fields in our data models.
capsargument has changed format due to the upgrade from GStreamer 0.10 to GStreamer 1. As far as we know, this is only used by Mopidy-Spotify. As an example, with GStreamer 0.10 the Mopidy-Spotify caps was:
audio/x-raw-int, endianness=(int)1234, channels=(int)2, width=(int)16, depth=(int)16, signed=(boolean)true, rate=(int)44100
With GStreamer 1 this changes to:
If your Mopidy backend uses
set_appsrc(), please refer to GStreamer documentation for details on the new caps string format.
capabilitiesargument is no longer in use and has been removed. As far as we know, this was only used by Mopidy-Spotify.
Duplicate seek events getting to
appsrcbased backends is now fixed. This should prevent seeking in Mopidy-Spotify from glitching. (Fixes: #1404)
tags_changedevents are only emitted for fields that have changed. Previous behavior was to emit this for all fields received from GStreamer. (PR: #1439)
Add partial support for gapless playback. Gapless now works as long as you don’t change tracks or use next/previous. (PR: #1288)
The Icecast docs has been updated with the workarounds still needed to properly stream Mopidy audio through Icecast.
Core playback has been refactored to better handle gapless, and async state changes.
Tests have been updated to always use a core actor so async state changes don’t trip us up.
Seek events are now triggered when the seek completes. Previously the event was emitted when the seek was requested, not when it completed. Further changes have been made to make seek work correctly for gapless related corner cases. (Fixes: #1305 PR: #1346)