New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for metadata lookup #263

Open
adamcik opened this Issue Dec 1, 2012 · 7 comments

Comments

3 participants
@adamcik
Member

adamcik commented Dec 1, 2012

Album model should be updated with an album art uri or similar. This also needs to be tied in to both local and spotify in some way and exposed in the http fronend if we don't go for just go data uris for now.

@jodal

This comment has been minimized.

Member

jodal commented Dec 3, 2012

I suggest that we use URIs in the cover art field, and not an URL, which means that it can contain either an URL or a data: URI. This makes it easy to get Spotify cover art included as data: URIs now. Later, if there is a need, we can make some sort of URI to URL conversion, where we host the cover art on disk or a web server.

Should we support more than one cover image?

Spotify only expose a single cover image. Seems like Last.fm does the same. Though, I can imagine having multiple images to offer if we some time in the future uses a cover art lookup service. Also when loading cover art from disk, I guess having the back side of the cover isn't unusual?

jodal added a commit to jodal/mopidy that referenced this issue Jan 6, 2013

adamcik added a commit that referenced this issue Jan 6, 2013

Merge pull request #314 from jodal/feature/album-images
models: Add Album.images field (#263)

jodal added a commit that referenced this issue Mar 12, 2013

@jodal

This comment has been minimized.

Member

jodal commented Mar 30, 2013

An images field was added to the Album model in pull request #314. The upcoming Soundcloud backend are already using this field for http URLs provided by Soundcloud, and the field is also in use by the Mopidy Lux web client.

We could probably close this issue, but instead I'm reusing it: The remaining part here is exposing Spotify album art as data: URIs.

@Florian95

This comment has been minimized.

Florian95 commented Apr 22, 2013

How to get all Album data (Like images) via the HTTP frontend ? "Lookup" just return a list of tracks.

@jodal

This comment has been minimized.

Member

jodal commented Apr 22, 2013

We've been talking of making library.lookup() return a SearchResult or similar, like library.search() already does, instead of just tracks.

You can either find Album objects via track.album or via a library.search().

Note that we currently don't expose Spotify album art.

@adamcik

This comment has been minimized.

Member

adamcik commented Apr 29, 2013

Most recent discussion of this seems to indicate we might want to change this to general metadata lookup API, that is not having images in tracks etc. but instead providing a core/backend library call to lookup and potentially set (for starred etc) metadata. Likely we would take a list of tracks and return a corresponding list of dicts.

@jodal

This comment has been minimized.

Member

jodal commented Sep 8, 2014

This bug is about adding a metadata lookup service or a more specific album art lookup service to Mopidy core.

mopidy/mopidy-spotify#23 is about making Spotify cover art available.

@adamcik

This comment has been minimized.

Member

adamcik commented Mar 14, 2015

Just to start collecting some other nodes on schemas etc:

http://microformats.org/wiki/music-examples
http://microformats.org/wiki/media-metadata-examples
https://musicbrainz.org/doc/MusicBrainz_Database/Schema

Currently I'm looking for something that can handle albums/tracks, podcasts, radiostreams (possibly with a station, show and current track), I've not considered things like concert bootlegs need any special handling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment