Mopidy 是一个音乐服务器，可播放来自多个源的音乐，例如你本地磁盘、无线电台、Spotify 和 SoundCloud 等。
Mopidy v0.19.0 发布，此版本主要是改进了 MPD 的实现，使用自身的 mixer API 代替 GStreamer mixers，可以使用 pip 安装 web 客户端。
此版本合并了 53 个 issues，12 位贡献者提交了 445 个 commits。
依赖
Mopidy now requires Tornado >= 3.1. Mopidy no longer requires CherryPy or ws4py. Previously, these
were optional dependencies required for the HTTP frontend to work.
后端 API
Commands
The mopidy-convert-config tool for migrating the setings.pyconfiguration
file used by Mopidy up until 0.14 to the new config file format has
been removed after over a year of trusty service. If you still need to
convert your old settings.py configuration file, do so using and older release, like Mopidy 0.18, or migrate the configuration to the new format by hand.
配置
日志记录
扩展支持
Breaking change: Removed the Extension methods that were deprecated in 0.18: get_backend_classes(),get_frontend_classes(), andregister_gstreamer_elements(). Usemopidy.ext.Extension.setup() instead, as most extensions already do.
Audio
Breaking change: Removed support for GStreamer mixers.
GStreamer 1.x does not support volume control, so we changed to use
software mixing by default in v0.17.0. Now, we’re removing support for
all other GStreamer mixers and are reintroducing mixers as something
extensions can provide independently of GStreamer. (Fixes: #665, PR: #760) Breaking change: Changed the audio/mixer config value to refer to Mopidy mixer extensions instead of GStreamer mixers. The default value,software,
still has the same behavior. All other values will either no longer
work or will at the very least require you to install an additional
extension. Changed the audio/mixer_volume
config value behavior from affecting GStreamer mixers to affecting
Mopidy mixer extensions instead. The end result should be the same
without any changes to this config value. Deprecated the audio/mixer_track
config value. This config value is no longer in use. Mixer extensions
that need additional configuration handle this themselves. Use Proxy configuration when streaming media from the Internet. (Partly fixing #390) Fix proper decoding of exception messages that depends on the user’s locale. Fix recognition of ASX and XSPF playlists with tags in all caps or with carriage return line endings. (Fixes: #687) Support simpler ASX playlist variant with <ENTRY> elements without children. Added target_state attribute to the audio layer’sstate_changed() event. Currently, it isNone except when we’re paused because of buffering. Then the new field exposes our target state after buffering has completed.
Mixers
Added new mopidy.mixer.Mixer API which can be implemented by extensions. Created a bundled extension, Mopidy-SoftwareMixer, for controlling volume in software in GStreamer’s pipeline. This is Mopidy’s default mixer. To use this mixer, set the audio/mixer config value to software. Created an external extension, Mopidy-ALSAMixer, for controlling volume with hardware through ALSA. To use this mixer, install the extension, and set theaudio/mixer config value to alsamixer.
HTTP frontend
CherryPy and ws4py have been replaced with Tornado. This will hopefully reduce CPU usage on OS X (#445) and improve error handling in corner cases, like when returning from suspend (#718). Added support for packaging web clients as Mopidy extensions and installing them using pip. See the HTTP server side API for details. (Fixes:#440) Added web page at /mopidy/ which lists all web clients installed as Mopidy extensions. (Fixes: #440) Added support for extending the HTTP frontend with additional server side functionality. See HTTP server side API for details. Exposed the core API using HTTP POST requests with JSON-RPC payloads at/mopidy/rpc. This is the same JSON-RPC interface as is exposed over the WebSocket at /mopidy/ws, so you can run any core API command. The
HTTP POST interfaces does not give you access to events from Mopidy,
like the WebSocket does. The WebSocket interface is still recommended
for web clients. The HTTP POST interface may be easier to use for
simpler programs, that just needs to query the currently playing track
or similar. SeeHTTP POST API for details. If Zeroconf is enabled, we now announce the _mopidy-http._tcp service in addition to _http._tcp.
This is to make it easier to automatically find Mopidy’s HTTP server
among other Zeroconf-published HTTP servers on the local network.
Mopidy.js client library
This version has been released to npm as Mopidy.js v0.4.0.
Update Mopidy.js to use when.js 3. If you maintain a Mopidy client, you should review the differences between when.js 2 and 3and the when.js debugging guide. All of Mopidy.js’ promise rejection values are now of the Error
type. This ensures that all JavaScript VMs will show a useful stack
trace if a rejected promise’s value is used to throw an exception. To
allow catch clauses to handle different errors differently, server side
errors are of the typeMopidy.ServerError, and connection related errors are of the typeMopidy.ConnectionError. Add support for method calls with by-name arguments. The old calling convention, by-position-only,
is still the default, but this will change in the future. A warning is
logged to the console if you don’t explicitly select a calling
convention. See the Mopidy.js JavaScript library docs for details.
MPD frontend
Proper command tokenization for MPD requests. This replaces the
old regex based system with an MPD protocol specific tokenizer
responsible for breaking requests into pieces before the handlers have
at them. (Fixes: #591 and #592) Updated command handler system. As part of the tokenizer cleanup
we’ve updated how commands are registered and making it simpler to
create new handlers. Simplified a bunch of handlers. All the “browse” type commands
now use a common browse helper under the hood for less repetition.
Likewise the query handling of “search” commands has been somewhat
simplified. Adds placeholders for missing MPD commands, preparing the way for bumping the protocol version once they have been added. Respond to all pending requests before closing connection. (PR: #722) Stop incorrectly catchingLookupErrorin command handling. (Fixes: #741) Browse support for playlists and albums has been added. (PR: #749,#754) The lsinfo command now returns browse results before local playlists. This is helpful as not all clients sort the returned items. (PR:#755) Browse now supports different entries with identical names. (PR:#762) Search terms that are empty or consists of only whitespace are no longer included in the search query sent to backends. (PR: #758)
Local backend
The JSON local library backend now logs a friendly message telling you aboutmopidy local scan if you don’t have a local library cache. (Fixes:#711) The local scan
command now use multiple threads to walk the file system and check
files’ modification time. This speeds up scanning, escpecially when
scanning remote file systems over e.g. NFS. the local scan
command now creates necessary folders if they don’t already exist.
Previously, this was only done by the Mopidy server, so doing a local scan before running the server the first time resulted in a crash. (Fixes: #703) Fix proper decoding of exception messages that depends on the user’s locale.
Stream backend
|
