by avand on 11/28/12, 8:07 PM with 19 comments
by brianwhitman on 11/28/12, 9:21 PM
Popularity of a single song: http://developer.echonest.com/api/v4/song/search?api_key=FIL...
List of songs by an artist ordered by popularity
http://developer.echonest.com/api/v4/song/search?api_key=FIL...
Since we have Rdio in our Rosetta ID space, you can natively use Rdio IDs and get them back in your calls:
http://developer.echonest.com/api/v4/song/search?api_key=FIL...
by diesellaws on 11/28/12, 9:21 PM
I may create a playlist one day based upon a certain artist (with similar artists in the mix) however the next day I may want to listen to something a bit heavier, making those playlists irrelevant no matter how far I've drilled down my preference list.
While Play Strength is a good concept, it's still just a feature that can become just as underused or overused as a star count.
Instead of focusing on how 'perfectly-automatic' we can make a playlist based on features such as genre, BPM & play strength, we should be focusing on tools that help better understand our moods, the environment around us & the energy and vibes we intend to create from the music itself. The Effect > The Cause.
by mw63214 on 11/28/12, 9:50 PM
by zeedog on 11/28/12, 9:20 PM
I also appreciate that many of the UI changes for these features are very subtle.
I just wonder how many users would actually find these features useful. I had to explain the concept of the "Collection" of a few people recently, which scared me since it's one of Rdio's core features!
by varikin on 11/29/12, 1:27 AM
The problem was two fold, one, I really love whole albums when done right. So that most of the music I listen to is album based. The markov chain is pointless then. Two, I would need a really big data set to make it worthwhile. Rdio has that data set (or possibly even Echo Nest).
by overcyn on 11/29/12, 4:07 AM
by JimEngland on 11/28/12, 8:39 PM