Mopidy Audio Server
- Unlike the old python version we do not wait for the first audio handoff, we only progress until the PAUSED state. This ensure we don't block on empty files. - Instead of using the signal watch and running the main loop we simply poll the messages from the bus directly allowing for a synchronous code flow. - Between each file the pipeline is always returned to NULL, this is done as we found that gst 0.10 will slow down as the uribin does not cleanup the children it creates for handling each file. This issue is not present in 1.0. - This also works around a segfault that was likely caused by a race condition that seems to trigger in the 0.10 version of the pbutils discoverer. - This version of the scanner also fixes the per track slow down, and works out to be considerably faster than even the built in discoverer from 1.0. - Finally this removes the WMA hack as I kan no longer find any evidence of it being needed. |
||
|---|---|---|
| data | ||
| docs | ||
| js | ||
| mopidy | ||
| requirements | ||
| tests | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| AUTHORS | ||
| fabfile.py | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| setup.py | ||
******
Mopidy
******
Mopidy is a music server which can play music both from multiple sources, like
your local hard drive, radio streams, and from Spotify and SoundCloud. Searches
combines results from all music sources, and you can mix tracks from all
sources in your play queue. Your playlists from Spotify or SoundCloud are also
available for use.
To control your Mopidy music server, you can use one of Mopidy's web clients,
the Ubuntu Sound Menu, any device on the same network which can control UPnP
MediaRenderers, or any MPD client. MPD clients are available for many
platforms, including Windows, 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 <https://github.com/mopidy/mopidy>`_
- `Issue tracker <https://github.com/mopidy/mopidy/issues>`_
- `CI server <https://travis-ci.org/mopidy/mopidy>`_
- `Download development snapshot <https://github.com/mopidy/mopidy/tarball/develop#egg=mopidy-dev>`_
- IRC: ``#mopidy`` at `irc.freenode.net <http://freenode.net/>`_
- Mailing list: `mopidy@googlegroups.com <https://groups.google.com/forum/?fromgroups=#!forum/mopidy>`_
- Twitter: `@mopidy <https://twitter.com/mopidy/>`_
.. image:: https://pypip.in/v/Mopidy/badge.png
:target: https://crate.io/packages/Mopidy/
:alt: Latest PyPI version
.. image:: https://pypip.in/d/Mopidy/badge.png
:target: https://crate.io/packages/Mopidy/
:alt: Number of PyPI downloads
.. image:: https://travis-ci.org/mopidy/mopidy.png?branch=develop
:target: https://travis-ci.org/mopidy/mopidy
:alt: Travis CI build status
.. image:: https://coveralls.io/repos/mopidy/mopidy/badge.png?branch=develop
:target: https://coveralls.io/r/mopidy/mopidy?branch=develop
:alt: Test coverage