I just finished day #2 at my new job. Sorry to be so cagey about where I was going, but they wanted to keep it quiet until they could do a press release about it. I see the press release is public now, so I’m free to talk about my new job.
As many of the commenters have guessed, I’ve joined, as the director of the developer community, The Echo Nest – a company that is devoted to providing music intelligence for the next generation of online music application. In this role, I will work with the rest of the Echo Nest team to help grow an active, vibrant music application developer community around The Echo Nest developer API.
I’m really excited to be here at The Echo Nest. The Echo Nest has already established a reputation as a company that provides a new breed of hardcore music intelligence. The Echo Nest goes far beyond the “wisdom of the crowds” model of music discovery (“People who listened to the Beatles also listened to the Rolling Stones”). Instead of just data mining user behavior, The Echo Nest crawls the web to learn everything it can about music by analyzing what the world is saying about music. The Echo Nest also directly analyzes the audio content of music – extracting musical traits such as key, tempo, structure, timbre from the audio.
From this analysis of the social context, the user behavior and the actual audio, the Echo Nest gets a deep understanding of the entire world music. It knows which artists are getting the most buzz, which artists are getting stale, how and why artists are related, what words are being used to describe the music. This data goes far beyond the “if you like Britney, you might like Christina” level. The Echo Nest understands enough about music to be able to answer queries such as “make me a playlist of songs with a tempo of 90 beats per minute by an unknown emo artist that sounds something like Dashboard Confessional, and has violins”. The really neat thing is that the Echo Nest is exposing a lot of this functionality in their developer API. This lets anyone who is building a music application to tap into this large resource of music intelligence.
One of my main duties is to be the voice of the developer in the Echo Nest. I’ve written my fair share of music apps, so I have a good idea of some of the many pain points and difficulties that a music application developer has to face, but I’d like to hear more, so if you are developing a music application and you need a particular problem solved let me know – or better yet, post to The Echo Nest developer forums.
I’ll be writing a lot about The Echo Nest in upcoming posts – in particular about using the developer APIs, but I shall still continue to post about all of the interesting things going on the music space – so this blog won’t be too much different from Duke Listens!