Both Gracenote and The Echo Nest play crucial, yet largely hidden roles in the digital music experiences of millions of consumers. Gracenote recognizes and identifies music that is initiated by users in various scenarios, such as loading a CD into a computer’s CD player. The Echo Nest’s technology underlies music recommendations, and powers radio-like experiences, in many leading music services. One reason (among several) that many music services have similar feature sets is that many of them use The Echo Nest’s API (Application Programming Interface) to power those features.
Still, the Echo Nest’s market leadership practically begs for opposition. Music recognition (Gracenote’s specialty) is different from music recommendation. But the description of Gracenote Rhythm’s API brings it patently into the recommendation realm: “When plugged into a music catalog, it gives developers the ability to create radio stations based on “seed” artists, songs, moods and genres with adaptive controls for “like” and “dislike,” ensuring next-generation radio stations get smarter and more personalized the more they are used. Developers will also control radio-tuning features that allow music fans to dial up more popular artists or dial down to receive more obscure, indie artists and tracks.”
From that description, Gracenote Rhythm sounds like it is tracking The Echo Nest’s mission exactly, perhaps offering qualitative differences rather than unique feature sets. But the beauty of API licensing is that the end result depends on collaborative development. The Echo Nest partnered with Xbox Music to create a unique feature called Web Play. (RAIN coverage here.) Gracenote Rhythm’s differentiation from The Echo Nest might depend on how much Gracenote developers can inspire music-service developers to innovate.