Analysis returning empty or zero

[Kevin Clark]

This is my first stab at using the Remix API and when using a few of
the demos I am not getting anything in return from the analysis. When
running the script, it'll say:

Analysis not found. Uploading...

when uploading is complete i try looking at for example analysis.tempo
or analysis.beat and they come up with values of (0.0, 0.0) and []
respectively.

also, the output file from the demos are consistently 1 second long of
silence.

Has anyone had this problem before and know what could be the problem?

[TeeJay]

Can you be a little bit more specific and show us what the terminal
tells you?
Are you using the latest version?

Analysis not found. Uploading... is normal if you've never run the
analysis on a given track before. The second time around, it will skip
the upload step.

T

[Kevin Clark]

I believe the version I am using is the latest. I used the installer
from: http://code.google.com/p/echo-nest-remix/

The terminal tells me this:

My input:
song = audio.LocalAudioFile("C:\Python26\echo-nest-remix-examples\music
\WhenIComeAround.mp3")

Response:
Computed MD5 of file is (code)
Probing for existing analysis
Echo Nest API Error 5: The Identifier specified does not exist: (code)
Analysis not found. Uploading...
en-ffmpeg -i "C:\Python26\echo-nest-remix-examples\music
\WhenIComeAround.mp3"
en-ffmpeg -y -i "C:\Python26\echo-nest-remix-examples\music
\WhenIComeAround.mp3" -ac 2 -ar 44100 "c:\users\kev\appdata\local\temp
\tmpdotwpn.wav"

My input:
song.analysis.beats

Response:
[]

My input:
song.analysis.tempo

Response:
('confidence': 0.0, 'value': 0.0)

I am not seeing an error but clearly I am not receiving any
information about the song.

[Graham Coleman]

Hi Kevin,

I'm definitely still getting this problem on Win7 for quite some time.

I found that if I upload the file previously using curl with a script,
then the next time I call Remix it recognizes the file and gets the
analysis fine:

curl -X POST -H "Content-Type:application/octet-stream" "http://
developer.echonest.com/api/v4/track/upload?
api_key=MYAPIKEY&filetype=mp3" --data-binary "@%1"

(I don't remember if this was my idea or if Reed suggested this to me)

When I talked to ATL at the BCN Music Hack Day recently, he suggested
that someone might have fixed this (what seems to be a windows
problem) in the latest source version.

Does someone know if this is the case? Has this been fixed?

cheers,

Graham

PS Hi Remix API community!