Forums » Bugs & Problems Search

Hi,

I just got:

Echo Nest API Error 8: Computation error (TRISTAN-0)

when running a King Tubby/Lee Perry track:

Computed MD5 of file is 1550c3335c7c76b4df58a7e27dfc48a4

I ran it again a couple minutes later and got:

Echo Nest API Error 5: Analysis not ready (please try again in a few minutes)

So I don't know whether the track is really still being analyzed, or whether the original error is stopping it from being analyzed at all...

thanks, douglas

drepetto:

I suspect that the track is never going to be analyzed because of the computation error. We should never see the computation errors, but such is life ... - we'll take a look to see what is going on with that particular track and will eliminate the computation error. However, it may be a bit before we can look at this particular problem.

Paul

Okay, thanks.

FWIW, I uploaded another similar track from the same collection (King Tubby Meets Lee Perry Megawatt Dub) and it analyzed just fine.

Computed MD5 of file is faaaabb64fceda2809c49274f8b1571f

douglas

And more FWIW, here's another TRISTAN-0:

Computed MD5 of file is cd879f6ebd14968b045fefe7005d212f

And moremoremore, if I convert the file to .wav and analyze it, it works fine. So I'm guessing it's a problem with the mp3 encoding on particular files. But you probably know that already! At least there's a workaround for files that won't analyze -- convert them to another format and try again.

useful. thanks drepetto. Just be glad you didn't get the dreaded TRISTAN-1 error. But seriously, this is a thing that is being looked at closely and we should be able to re-render for you the ones you listed soon. -B

yeah i just got " Echo Nest API Error 8: Computation error (TRISTAN-0)" also, on a batch op. had Echo Nest API Error 5: Analysis not ready (please try again in a few minutes) a few times also. Its not a huge deal, but are there specs we should follow or be aware of in regards the mp3 format?

jamess:

Sorry for the troubles. We are working to fix these issues. All MP3s should be analyzable, you should not have to follow any guidelines. As long as your MP3 is a real MP3 it should analyze. If an MP3 doesn't analyze, that's our problem to fix.

Paul

I'm getting a persistent "Echo Nest API Error 5: Analysis not ready (please try again in a few minutes)" on
MD5 = b94550ab0b2648e902c74c8f042531e2

Is there a particularly long queue running right now, or is this long track (1116 secs, 34.1MB) just too big?

atl:

The queue is up and running. I just uploaded a short MP3 file and analyzed it with no troubles. I don't know of any size limits. The engineers will be arriving in a bit, when they come in, we'll take a look to see what has gone askew.

Paul

atl:

As for the file with MD5 b94550ab0b2648e902c74c8f042531e2 - there was a computation error on the file, but the web tier wasn't detecting that status and reporting it properly.

P