https://github.com/mopidy/mopidy/blob/2ee130057113d7c0b46e16a0d7c19180614d5bd9/mopidy/core/tracklist.py#L370

Is this intentional to not return previous track when repeat mode is enabled ?

I installed 0.7.0 today and copied my streamuris.js from 0.6.0 but my stream list is not updating. Does 0.7.0 store the streamuris.js in a different folder or is the file format different?

If the dbus interface is misbehaving, commands can hang forever. We should add a timeout to exit in a timely manner, maybe 5 seconds.

Since pytest-3.0, fixtures using the normal fixture decorator can use a yield statement to provide fixture values and execute teardown code, exactly like yield_fixture in previous versions.

Marking functions as yield_fixture is still supported, but deprecated and should not be used in new code.

https://docs.pytest.org/en/latest/yieldfixture.html

In the pimusicbox Web Frontend is no update of the stream title. The method core.playback.get_stream_title from the mopidy core library gives exactly the information needed, but there is no function implemented to call this from the "now Playing" view in the web frontend. Seems to me that this is "...one small step for man, one giant leap for mankind." :-)

I'm using gmusic over MPD with ncmpcpp and I wondered if there was any way to add my google music library to the media library view (see screenshot). I'm guessing not and that the media library is your local media only. Can you trick it with something like

[local]
library = gmusic

Either way, mopidy plus gmusic is awesome!!! Thanks so much.

![screenshot from 2017-01-20 22-5

the plan is to develop on top of the Mopidy javascript library.

it will be great to integrate the LED matrix APIs so a user could draw on it directly from the same web-interface (or maybe the we could get more ambitio

It would be nice to be able to set the minimal time a track has been played to be scrobbled in mopidy's config file. would only be a couple of lines of code....

As discussed in https://discuss.mopidy.com/t/unable-to-create-a-playlist-from-a-podcast-uri-in-mopidy-js/737, clients sometimes may want to create models by themselves, e.g. to add tracks to playlists. Currently, this is only possible by creating a plain JS object with the semi-documented __model__ property.
Although the use case discussed above concerns the playlist API, there may be other case

As of Mopidy-Beets 4.0.0rc1, the Album.images field is no longer set, as the field no longer exists in Mopidy 3.0. We should implement support for the replacement, LibraryProvider.get_images().

See the docs at https://docs.mopidy.com/en/latest/api/backend/#mopidy.backend.LibraryProvider.get_images

This is a very interesting project to me because it seems like one of the few attempts to make a single cohesive control system for Snapcast and actual audio sources (Spotify, Google Music, etc). I've toyed with the idea of building something similar, just haven't found the time, so I'm intrigued with this project. But it's not clear to me how it works. Does HydraPlay spawn a new Snapcast server i

Provide some examples and/or hints of how to make use of the Autoplay Url feature. Musicbox docs also needs something, could link to that.

Before we go into customizing styles too much, would be good to have latest version available (still in alpha tough) http://blog.getbootstrap.com/2015/08/19/bootstrap-4-alpha/

• Use case: Run Mopidy-MPRIS + Rygel on a headless system to support playing audio in Mopidy from an UPnP client.
• Research: Does any MPRIS clients support using the system bus?
• Research: Can we start a session bus if there's none? Ref. wrap-dbus script. Will Rygel running as some other user on the system be ab