|
Posts: 27
Registered: Mar 29, 2009
|
Posted: 2009-12-18 05:42:18
|
I have noticed that tracks over some size or length never succeed analysis. Is this a documented cap on the size or length of tracks that EchoNest will accept? I noticed this when trying to analyze tracks from Tangerine Dream's "Poland" album.
|
|
|
Posts: 666
Registered: Sep 08, 2008
|
Posted: 2009-12-18 10:53:44
|
Hi ChrisM - we limit analysis to tracks that are less than an hour long. But it looks like fro the Wiki page that the tracks might be shorter than that. If indeed you are having trouble analyzing 20 minute tracks please let us know. Also, check to ensure that you are using analysis_version=3 for your analysis, analysis_version=1 was not very stable when analyzing very long tracks.
Paul
|
|
|
Posts: 27
Registered: Mar 29, 2009
|
Posted: 2009-12-21 03:00:02
|
Paul,
Thanks for the response.
Indeed, I have tracks with durations of 22:36, 21:34, 21:11, 19:37, and 18:12 that all fail analysis. I have one track of duration 18:33 that has succeeded. All of my tracks shorter than 18:03 (over 2700 tracks) have succeeded. I could provide md5 hashes for the failing tracks if that would help in any way.
ChrisH
|
|
|
Posts: 666
Registered: Sep 08, 2008
|
Posted: 2009-12-21 11:44:53
|
ChrisH: We'll take a look. If you have the MD5 hashes that will help. Also, can you verify that you are using analysis_version=3?
Paul
|
|
|
Posts: 27
Registered: Mar 29, 2009
|
Posted: 2009-12-21 17:35:30
|
Paul,
Yes, I am using analysis_version=3 via your Java API.
Here are the MD5s for my six longest tracks:
- ccbb5686ffa7a5530431fe8b577775be (dur: 22:36)
- 2d785ba9a8b3fc90f58b82387ac4a4dc (dur: 21:34)
- fe0bff49e7f17c06b15470c7e8814a0e (dur: 21:11)
- 49e89e1a792525a468e5b77d35a9d6d7 (dur: 19:37)
- d919c695fb08e029100114cefcb72fdf (dur: 18:33, this one works)
- 7ae95d33ff3ff1eafff6a0a62f15f140 (dur: 18:12)
Chris
|
|
|
Posts: 666
Registered: Sep 08, 2008
|
Posted: 2009-12-21 17:36:37
|
Thanks ChrisH. We'll take a look
Paul
|
|
|
Posts: 666
Registered: Sep 08, 2008
|
Posted: 2009-12-22 13:43:15
|
ChrisH - we've been able to duplicate the problem - so it is something we can fix. I'll let you know when the issue has been resolved.
Paul
|
|
|
Posts: 27
Registered: Mar 29, 2009
|
Posted: 2009-12-23 05:48:14
|
Thanks, Paul. Kudos to you and the whole EchoNest team for being so responsive.
Chris
|
|
|
Posts: 27
Registered: Mar 29, 2009
|
Posted: 2010-04-22 14:54:23
|
Has there been any progress towards fixing this problem?
|
|
|
Posts: 666
Registered: Sep 08, 2008
|
Posted: 2010-04-28 11:16:34
|
Hi Chris, sorry for the delay - the amsterdam music hackday activities dominated our engineering efforts for the last few weeks. I'll get you an update on this today. -- Paul
|
|
|
Posts: 27
Registered: Mar 29, 2009
|
Posted: 2010-05-03 17:46:55
|
|
Posts: 11
Registered: Sep 20, 2009
|
Posted: 2010-05-05 13:41:01
|
Hey there ChrisH,
This issue has been fixed for the next release. When's the next release, you ask? That's yet to be determined, but we'll update you when we work out a timeframe.
(Apologies for the noncommittal response, but we just wanted to keep you informed).
-Mark
|
|
|
Posts: 27
Registered: Mar 29, 2009
|
Posted: 2010-05-07 19:30:09
|
Thanks, Mark.
Sounds good. I've been reading about the new features coming with the next release and I am looking forward to it.
Chris
|
|
|
Posts: 1
Registered: Sep 09, 2008
|
Posted: 2010-07-16 16:07:32
|
A related question: is there also a limit on the file size, as opposed to the song length? I have several WAV files that I'm trying to analyze, but everything over ~34MB or 35MB is failing (curl: (52) Empty reply from server). Is this correct behavior?
|
|