Forums » Bugs & Problems Search

Hello. I re-attempted beat extraction for tracks that had been analyzed beforehand through echonest, but I now get Error Code 11 each time (via the Processing API recently created). Newly uploaded tracks have no problem however. I'm not sure what the issue is. Thank you.

zeeshanlakhani:

We have just switched our analysis methods to use our new and improved analyzer by default (analysis_version=3). This means that all new upload tracks will be analyzed with the new version and any requests for analysis data (such as getting beats) will look for analysis_version=3 data. New analyzer gives better data and is much more stable than the previous version, so we recommend that you use it, that is why it is now the default. You can get to the old analysis data by setting the new 'analysis_version' parameter to 1. For example:

http://developer.echonest.com/api/get_beats?api_key=your-key&id=music://id.echonest.com/~/TR/TRLFPPE11C3F10749F&version=3&analysis_version=1

will get beats from a version 1 analysis.

To see if a track already has an analysis for a given version you can call get_metadata with analysis_version set to the desired version. If the analysis status is COMPLETE then there is an analysis available, if the status is UNAVAILABLE this means that we know about the track but we haven't analyzed it yet - in which case you can reanalyze the track using the 'analyze' method.

So here's what a track uploader should do:

1. Get the Md5 for the track
2. call get_metadata with the MD5
3. If the analysis status is UNKNOWN upload the track
4. If the analysis status is UNAVAILABLE call analyze with the md5
5. If the analysis status is COMPLETE, the data is ready, call get_beats etc

Hope this helps.

Paul

Hey Paul. I'm still getting Error Code 11 on the songs that I had uploaded previously. All "new" tracks work without issue. Is there a way that the tracks I previously uploaded get removed from the system, allowing me to reupload them as new tracks? Anyway, thanks for your help.

Zeeshan

Hi Zeeshan, could you please post some examples of the tracks giving you Error Code 11? We would like to investigate. Many thanks!

Sure.

Here are two titles:

1_NIN-The Hand That Feeds_original.mp3 Bite the hand that feeds - Gluttony remix.mp3

There's like 50 that had the problem. Again, tracks that I upload now (never analyzed before) work without issue.

Thanks.

Zeeshan

Thanks - do you happen to have md5 or track ids (TR...) for these?

I don't. I've been running these through Melka's Processing library. I've discussed the issue with him, and he hasn't had any issues with previously analyzed tracks. So, I'm not sure. Thanks.

Zeeshan

To get the md5 for a file on the Mac (which I'm assuming b/c you reference Melka's work), open a Terminal.app window and type "md5 -q " (without the quotes, but with the trailing space), and then drag the MP3 file into the Terminal window. Hit enter in the terminal window, and then cut & paste that big hex string into this forum.

Thanks atl! Also, please make sure that you do pass analysis_version=1 parameter on the call - otherwise you will get Error 11 for the tracks previously analyzed.

Thanks atl for the md5 hint.

Here are the two md5's for the songs I posted before: 3a7a5a6a68e400091b6b37e3096587a5 adb45dfd08d0017a4ee79e9c85bb3da3

I'm not sure if Melka's library allows for the pass offhand. I emailed him about it.

Zeeshan

Zeeshan, thank you very much for md5. It is indeed the case of missing analysis_version parameter. As Paul mentioned in the beginning of this thread we changed the default analysis_version to 3 to ensure the use of the latest analyzer. That means that to get the analysis data of previously uploaded tracks you need to pass analysis_version=1 to the call explicitly, e.g.: http://developer.echonest.com/api/get_segments?analysis_version=1&api_key=&md5=3a7a5a6a68e400091b6b37e3096587a5&version=3 I checked it and it works fine for the call above. Hope it helps! Thanks

Right. But, would it be possible for me to reanalyze the tracks...from scratch...using the newest version?

Zeeshan

P.S. Hopefully that's not a redundant question.

Hi everyone Zeeshan contacted me about the error code 11 so I've changed the processing wrapper library a bit.

1st Change : You can specify which version you want to use for the analysis. The default method is using the analysis_version=3: EchoNest nest = new EchoNest(this,APIKey,fileToUpload); For the tracks that gives error code 11, you add a parameter : EchoNest nest = new EchoNest(this,APIKey,fileToUpload,1);

2nd Change : I did not like the fact that the sketch was hanging while downloading all the datas, so I added a new mechanism. All the requests are done in a different thread, and when you init you ENTrack object, all the datas available are downloaded. The echonest object then sends a notification to the sketch. You have to add this function to your code : void ENTrackLoaded(ENTrack track) { } It's called when everything is loaded.

I updated the example in the library, so check it out to have more infos.

You can download the new version on googlecode : http://code.google.com/p/echonestp5/downloads/list

Please tell me if that works for you.

Cheers.

melka

Thanks Melka. I will try the new processing version later tonight. However, I would still like to reanalyze the songs with the new analysis version if it were possible to do so without the error. That's more of a general echonest question though.

Thanks.

Zeeshan

Hi Zeeshan, you can reanalyze the tracks using new analyze method available on the developer.echonest.com It is a POST method Hope it helps, thanks!