Mopidy Audio Server
a3ab956733
This makes track lookup behave consistently with lookup of artists, albums and playlists. I consider this "safe", since track lookup is only used for lookup of single tracks by URI. If you're e.g. loading a playlist full of unloaded tracks, you should still use SpotifyTrack to avoid blocking on track loading. |
||
|---|---|---|
| bin | ||
| data | ||
| docs | ||
| js | ||
| mopidy | ||
| requirements | ||
| tests | ||
| tools | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| AUTHORS | ||
| fabfile.py | ||
| LICENSE | ||
| MANIFEST.in | ||
| pylintrc | ||
| README.rst | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
****** Mopidy ****** .. image:: https://secure.travis-ci.org/mopidy/mopidy.png?branch=develop Mopidy is a music server which can play music both from your local hard drive and from Spotify. Searches returns results from both your local hard drive and from Spotify, and you can mix tracks from both sources in your play queue. Your Spotify playlists are also available for use, though we don't support modifying them yet. To control your music server, you can use the Ubuntu Sound Menu on the machine running Mopidy, any device on the same network which can control UPnP MediaRenderers, or any MPD client. MPD clients are available for most platforms, including Windows, Mac OS X, Linux, Android and iOS. To get started with Mopidy, check out `the docs <http://docs.mopidy.com/>`_. - `Documentation <http://docs.mopidy.com/>`_ - `Source code <http://github.com/mopidy/mopidy>`_ - `Issue tracker <http://github.com/mopidy/mopidy/issues>`_ - `CI server <http://travis-ci.org/mopidy/mopidy>`_ - IRC: ``#mopidy`` at `irc.freenode.net <http://freenode.net/>`_ - `Download development snapshot <http://github.com/mopidy/mopidy/tarball/develop#egg=mopidy-dev>`_