tooxie / shiva-server

A RESTful API to your music collection
http://shiva.readthedocs.org/en/latest/intro.html
MIT License
556 stars 51 forks source link

Replace the concept of playlists #7

Open tooxie opened 12 years ago

tooxie commented 12 years ago

Maybe they shouldn't be replaced, but at least they should not be as important as they are in most players. I think amarok got it right, it's all about the artists. You search for artists, then maybe for albums, but for that all the files have to be correctly tagged. A good tagging GUI is key.

Playlist should come into play in those cases where you want, for example, different songs from the same artists or from a given genre. But mostly, you build the currently-playing playlist by going through the artists.

Freso commented 11 years ago

I actually mostly use "dynamic playlists" with e.g. XBMC "all tracks in these genres, except (the ones by this or this artist) or (rated below average)".

Being able to generate a dynamic playlist based on similar music would also be a nifty "replacement".

celaus commented 11 years ago

similar to issue #25 shiva could use the echonest ( http://the.echonest.com ) for identification (e.g. with echoprint http://echoprint.me) and playlist generation based on all kinds of aspects (similarity, ...). It also comes with a nice official python library https://github.com/echonest/pyechonest that could be used for both features.

tooxie commented 11 years ago

Is this the client's responsibility or should this be baked into shiva-server? Now that I think about it maybe Shiva should just provide the listing of artists and the possibility of creating playlist. But the server should not enforce any approach.