search

Mach5 / supersonic

Open-source web-based media streamer and jukebox fork of Subsonic. Supports MP3, OGG, AAC and other streamable audio and video formats. Runs on Windows, GNU/Linux and Mac using Java.
228 stars 61 forks source link

Intelligent playlist generation to allow for automated listening based on user preferences #5

Open porkcharsui opened 12 years ago

porkcharsui commented 12 years ago

EchoNest integration?

trapexit commented 12 years ago

In the least a way to have random songs regularly added so it's not necessary to constantly keep adding sets of 50 songs to the playlist.

timoreimann commented 12 years ago

bile, there's already a feature called shuffle play which keeps fetching and playing random songs. Is that what you possibly refer to?

trapexit commented 12 years ago

In Android, yes. I'm referring to the webui. Unless I'm missing something shuffle in the webui only takes the existing playlist and randomizes it. I'd like to see something like Last.FM or Pandora. Random play based on some criteria. Artist, year, using EchoNest, etc. Like the "Random Playlist" feature but in realtime similar to Android. I don't want 50 random songs. I want infinite :)

And it more prominently displayed in the interface. Not hidden away in "More."

timoreimann commented 12 years ago

Ok, I missed you were referring to the Web UI. Bringing shuffle play from the Android implementation to the front-end could serve as a starter though, so it's good to be documented here.

porkcharsui commented 12 years ago

@bile I just walked through all the current "random" functionality in the webui and it definitely needs help. After first selecting "play random," running out of songs stops playback when your playlist completes. It appears never to fetch more music so you would have to again click and prime it all while hoping the UI doesn't give you songs you just heard.

I'm still investigating how to handle syncing your local collection to Echonest as input into the "random playlist" request as it appears to a feature of the API. Each user would need an API key for Echonest in the type of setup, so some additional messaging will be need to direct admins to signup for this.

This feature needs top level placement like you suggest as in other music interfaces like Apple's "Genius" or Google's "Instant Mixes."