Issue with the JSON object about echoprintforandroid HOT 6 CLOSED

Hi Soundmaven,

It is quite possible that echonest changed the implementation of their server, however, looking at the published demo server source (https://github.com/echonest/echoprint-server/blob/master/API/api.py), I can still see the required values, except for the metadata entry:

return json.dumps({"ok":True, "query":stuff.fp_code, "message":response.message(), "match":response.match(), "score":response.score, "qtime":response.qtime, "track_id":response.TRID, "total_time":response.total_time})

I no longer have a separate server for testing, but looking at the echoprint.me page, I see that they have been fixing bugs and that the response now looks like:

{"response": {"status": {"version": "4.2", "code": 0, "message": "Success"}, "songs": []}

Which doesn't have a "match" section, instead now has a "songs" array with the potential matches. You may want to modify the code so it checks for the number of entries in the songs array. That is what they seem to be doing now in their iOS example code.

As far as I can see the codegen hasn't changed, so the code that generates the fingerprints should still work.

Hope that helps!

Alex.

from echoprintforandroid.

Hi Alex,

Thanks for the response. I've already modified the code and got it working. I have two more questions though, if you don't mind. I'm just starting looking into EchoPrint and would appreciate any advice or info you can give.

1. There is, let's say, inconsistency in the way fingerprinting works. For example, I'm often getting an empty response on a song that was successfully identified just a minute ago. The result string then looks like this: result: {"response": {"status": {"version": "4.2", "code": 0, "message": "Success"}, "songs": []}}. It's funny, but I have two phones sitting side by side running the example app and sometimes on one of them the app can successfully identify what song the other is playing, while on that phone it fails to do it.

Do you know the reason for this inconsistency, and are there any ways to improve the matching performance? I thought about increasing the listening time, but I believe 20 seconds is already long enough, at least from the user's standpoint.

Just for the information, I'm using a SERVER_URL of "http://developer.echonest.com/api/v4/song/identify?api_key=my_key&version=4.11&code=my_code";

2. Was there any reasoning behind setting minSDKVersion to 11 (which is 3.0, AFAIR)? Everything seems to work fine on earlier versions.

I also can't seem to find the iOS example code you're referring to, and I'd love to take a look at it. Could you share a link maybe?

Thanks in advance!

from echoprintforandroid.

Sorry for the delay!

Yes I did notice some inconsistency, but worked most of the time for me with samples ranging from 15 to 20 seconds.

The minimum version for the SDK was simply because at the time Is how I had my environment set up, I never tried it below 11, but I guess it works :)

As for the iOS sample, you can find it here:
https://github.com/echonest/echoprint-ios-sample

Alex.

from echoprintforandroid.

Hello im new in programming . can i have the solution to fix the "Unknown Error" after this line code

\ parse JSON
JSONObject jobj = new JSONObject(result);

please help me :( thx

from echoprintforandroid.

Hello soundmaven,

What changes did you make to the code for it to work?

from echoprintforandroid.

Hi There,

You can read the details here http://masl.cis.gvsu.edu/2012/01/25/android-echoprint/

On May 26, 2014, at 7:42 AM, joshafc [email protected] wrote:

Hello soundmaven,

What changes did you make to the code for it to work?

—
Reply to this email directly or view it on GitHub.

from echoprintforandroid.