All,
We are currently experiencing an outage effecting all calls to the Echo Nest API. We are working hard to resolve the issue now and will provide additional information as we have it. We apologize for the interruption. -- Paul
All,
We are currently experiencing an outage effecting all calls to the Echo Nest API. We are working hard to resolve the issue now and will provide additional information as we have it. We apologize for the interruption. -- Paul
curl -i 'http://developer.echonest.com/api/v4/artist/profile?api_key=MYKEY&name=weezer' HTTP/1.1 200 OK Date: Wed, 02 Apr 2014 13:33:30 GMT Content-Type: application/json; charset=utf-8 Content-Length: 135 Vary: Accept-Encoding X-Request-Id: n6JeADA+QiSaCOhN9ZRupw Etag: "f4d21835f2fd32fde0155c86f9304abd7ef60055" X-Worker-Node: 62c18:21727 X-Ratelimit-Remaining: 19 Server: TornadoServer/3.1 X-Ratelimit-Limit: 20 X-Api-Key: LG9LT6MZQJCLRMFVS Cache-Control: max-age=86400 Access-Control-Allow-Origin: * X-Ratelimit-Used: 1 Connection: Keep-alive Keep-Alive: timeout=15, max=100 Via: 1.1 ID-0000627501223746 uproxy-2
{"response": {"status": {"version": "4.2", "code": 0, "message": "Success"}, "artist": {"id": "AR633SY1187B9AC3B9", "name": "Weezer"}}}
It now seems to be working fine..... How common are these transient errors?
Full service has been restored. -- Paul
We experienced a rare API outage this morning. We will follow up with more details soon. Such outages are relatively rare. The last one occurred in October. -- Paul
Yes, it's working fine now ! I supposed theses errors were du to the echonest server problem !
Full service has been restored. Apologies for the outage. -- Paul
Modern Assembly is looking for a creative developer who knows the echonest api very well and can help us build an amazing new tool for a high profile brand partnership with Spotify.
We can't share details in this blog posting, but it's the type of project that requires:
We are looking for an independent contractor who can work on a fixed fee or hourly basis. Experienced candidates only please.
We look forward to hearing from you!
Paul Aaron Co Founder Modern Assembly paul@modernassemb.ly
Hi, I am having some problems getting uploadTrack on Android to work. I don't really know much about coding. This is my code:
EchoNestAPI en = new EchoNestAPI(API_KEY); String path = songsList.get(song_Index).get("songPath"); File file = new File(path); if (!file.exists()) { System.err.println("Can't find " + path); } else { try { track = en.uploadTrack(file); track.waitForAnalysis(30000);
The program quits for the line track = en.uploadTrack(file); The only messages the log shows are 04-03 15:15:39.996: D/AndroidRuntime(1139): Shutting down VM 04-03 15:15:40.016: W/dalvikvm(1139): threadid=1: thread exiting with uncaught exception (group=0xb1ab5ba8) 04-03 15:15:40.156: E/AndroidRuntime(1139): FATAL EXCEPTION: main 04-03 15:15:40.156: E/AndroidRuntime(1139): Process: com.revItUp.musicPlayer, PID: 1139
Any tips?
Did you add proper permissions to your manifest?
See
http://developer.android.com/training/basics/network-ops/connecting.html
for details.
-- Paul
I added the permissions but nothing changed.
-Andrew
The songs bucket of the artist API seems to return many duplicate entries. Using the docs example, the first 3 results are all for "Creep": http://developer.echonest.com/api/v4/artist/songs?api_key=API_KEY&id=ARH6W4X1187B99274F&format=json&start=0&results=10
Is there any way to have the songs bucket only return unique title results?
volkerdassler - the best way to ensure no duplicates is to use the playlist API. For example:
http://developer.echonest.com/api/v4/playlist/static?api_key=YOUR_API_KEY&artist=radiohead&sort=song_hotttnesss-desc
will return a unique set of songs by radiohead, roughly sorted by descending hotttnesss.
Paul
As always, thanks for the quick response, Paul! This totally helps. - Jordan
Apologies if this has already been asked but search wasn't working.
In regards to the track audio_summary result/fields (i.e. danceability, energy, loudness, speechiness, liveness, ...) - it is right to assume (and can someone confirm) that the majority have the ranges 0.0-1.0 with the exception of loudness (what is this a measurement of) and tempo.
If not then is it possible to have the range value for each?
Cheers, J
Im brand new to using this service. It seems like a big waste of resources (for both Echonest and the end user) to continue to upload the rest of a song; even if the song can already be detected from the first part of the song.
It would be great if Echonest could cancel the upload as soon as the media file is detected; and, subsequently returning the song information.
MKANET - the efficient way to do what you want is to extract FP hashes locally on your device and send those to the song/identify method for identification. See http://echoprint.me/ for details on how to go about this. -- Paul
josh,
See this page for details on each of the acoustic attributes. Yes, each of these ranges from 0.0 to 1.0. The other properties in the audio_summary represent more objective musical features (tempo, key, mode, etc.) and have unique values. Probably the most complete breakdown of values is found in the song/search documentation.
Loudness is a weighted average of the volume across the entire track.
David
Thanks for the reply. However, the call you specified returned this:
{"response": {"status": {"version": "4.2", "code": 0, "message": "Success"}, "songs": [{"artist_id": "ARLHO5Z1187FB4C861", "title": "Intergalactic (Digitally Remastered 99)", "id": "SOLHFWG12B0B80B78F", "artist_name": "Beastie Boys", "artist_foreign_ids": [{"catalog": "rdio-US", "foreign_id": "rdio-US:artist:r232323"}]}]}}
There's still on Rdio track ID being returned there. I'd like to be able to get the Rdio track ID based on a WhoSampled track ID.