Forums » Bugs & Problems Search

I try to analyze some chinese song. when I upload "周杰倫-蝸牛"

API return: { "response":{ "status":{ "version":"4.2", "code":0, "message":"Success" }, "track":{ "status":"complete", "samplerate":44100, "bitrate":64, "audio_md5":"40c7f7e5351f993dae79aee4c3bf27b8", "md5":"3ac7031084c2e32d29b783bf69eff731", "artist":"", "title":"", "id":"3ac7031084c2e32d29b783bf69eff731", "analyzer_version":"3.1.0_beta_5", "release":"" } } }

the track id should be something like 'TR......' but I got the same id with md5 code

how can I get the correct id so I can use analyze API

Thanks for reply

I am having this exact same issue.

I've been having the same issue breaking my code for a few days.

The song ID being returned by upload is the same as the MD5, but it doesn't work - analyze and profile don't work if I try to use it as an ID (-1/"The Identifier specified does not exist" or 5/"Unknown error").

In addition, analyze is failing when I try to specify the md5 rather than an ID. (And, of course, I can't find out the ID of a new upload, due to the previous issue.)

jlw, lgarron,

Could you post the response you get from track/upload and, if possible, make the audio available for us to investigate?

Thanks. David

This is my case:

audio url: http://dctlab.nccu.edu.tw/wp-content/uploads/2012/05/snail.mp3

upload post:

curl -X POST "http://developer.echonest.com/api/v4/track/upload" -d "api_key=N6E4NIOVYMTHNDM8J&url=http://dctlab.nccu.edu.tw/wp-content/uploads/2012/05/snail.mp3"

return json:

{"response": {"status": {"version": "4.2", "code": 0, "message": "Success"}, "track": {"status": "complete", "artist": "", "title": "", "analyzer_version": "3.1.0_beta_5", "release": "", "audio_md5": "0adcf60ae030663675d2b789365a0514", "bitrate": 64, "id": "3ac7031084c2e32d29b783bf69eff731", "samplerate": 44100, "md5": "3ac7031084c2e32d29b783bf69eff731"}}}

fukuball,

This is a bug in how we handle new uploaded tracks. The "id" in the response should be an Echo Nest "TR..." track ID instead of the MD5 of the file. We're looking into it. Thanks for your patience.

David

fukuball, jlw, lgarron,

We addressed this issue on Friday with an API update. Many tracks uploaded from Apr 30 to May 4 that received an invalid "id" in the reply (an id not beginning with "TR") should now be uploaded again to generate a proper Echo Nest TRID. From there, you should be able to call track/profile with the TRID returned.

I get the following proper response from the curl example above:

{"response": {"status": {"version": "4.2", "code": 0, "message": "Success"}, "track": {"status": "complete", "artist": "", "samplerate": 44100, "title": "", "analyzer_version": "3.1.0_beta_5", "release": "", "audio_md5": "40c7f7e5351f993dae79aee4c3bf27b8", "bitrate": 64, "id": "TRMJODQ1372DE2B865", "md5": "3ac7031084c2e32d29b783bf69eff731"}}}

We apologize for the inconvenience this issue caused. Please let us know if any issues remain with track/upload.

~David

It seems to be returning "TR..." track ids instead of md5 as the track id now. Thanks.

I did notice that when I search for a song using the song/search API, it gives a TRID in the response. With that TRID, I find its 30-second preview from the 7digital-US catalog, and then upload the preview using track/upload API, which returns a different TRID than the one for the original song. Are TRID's unique to the audio file?

jlw,

Yes. TRIDs are unique to audio files. The same song may have many different tracks in various catalog id spaces. The 30-second preview you get from 7digital-US is different from the full track.

David

Dear David,

It works! I am very appreciate your work!