Quantcast
Channel: The Echo Nest Developer Forum
Viewing all 1582 articles
Browse latest View live
↧

Check taste profile status

June 11, 2014, 4:44 am
$
0
0

Droped

this is what I have in json now: {"action":"update","item":{"item_id":"1_1","song_name":"The Look of Love","artist_name":"Dusty Springfield","favorite":true}},

And after check status I still get:

[status] => stdClass Object ( [version] => 4.2 [code] => 0 [message] => Success )

[total_items] => 29499
[items_updated] => 29499
[percent_complete] => 100
[ticket_status] => complete
[update_info] => Array
    (
        [0] => stdClass Object
            (
                [item_id] => 10000_5984
                [info] => couldn't resolve item
            )

        [1] => stdClass Object
            (
                [item_id] => 10001_5985
                [info] => couldn't resolve item
            )

        [2] => stdClass Object
            (
                [item_id] => 10002_5986
                [info] => couldn't resolve item
            )
↧
Search

Check taste profile status

June 11, 2014, 5:13 am
$
0
0

Try uploading in smaller batches; maybe 1000 or 2000 songs at a time?

↧
↧

Check taste profile status

June 11, 2014, 6:04 am
$
0
0

Ned, thanks for your help

But it still the same. Here is the response:

[status] => stdClass Object ( [version] => 4.2 [code] => 0 [message] => Success )

[total_items] => 1001
[items_updated] => 1001
[percent_complete] => 100
[ticket_status] => complete
[update_info] => Array
    (
        [0] => stdClass Object
            (
                [item_id] => 1001_750
                [info] => couldn't resolve item
            )

        [1] => stdClass Object
            (
                [item_id] => 100_86
                [info] => couldn't resolve item
            )

        [2] => stdClass Object
            (
                [item_id] => 101_87
                [info] => couldn't resolve item
            )

For all 1001 rows it returns "couldn't resolve item" :( May be something wrong with my API key?

↧

Check taste profile status

June 11, 2014, 6:53 am
$
0
0

Hi there,

An update for a taste profile item that already exists only changes the fields that are actually present in the data you post. In order to remove the song_id and artist_id fields, you need to set them to null in your source JSON file. Or, you can delete the taste profile and start over again, if that's easier.

↧

Check taste profile status

June 11, 2014, 7:20 am
$
0
0

Hi, Thanks for your help. Now json format is:

{"action":"update","item":{"item_id":"1_1","song_id":null,"song_name":"The Look of Love","artist_id":null,"artist_name":"Dusty Springfield","favorite":true}},{"action":"update","item":{"item_id":"2_2","song_id":null,"song_name":"Look After You","artist_id":null,"artist_name":"The Fray","favorite":true}}

with "song_id":null and "artist_id":null

I have created new taste profile and at the end I have:

[version] => 4.2 [code] => 0 [message] => Success )

[total_items] => 1001
[items_updated] => 1001
[percent_complete] => 100
[ticket_status] => complete
[update_info] => Array
    (
        [0] => stdClass Object
            (
                [item_id] => 1001_750
                [info] => couldn't resolve item
            )

        [1] => stdClass Object
            (
                [item_id] => 100_86
                [info] => couldn't resolve item
            )

The same result as before. For all items it returns "couldn't resolve item" message.

↧
↧

Check taste profile status

June 11, 2014, 7:43 am
$
0
0

Your new taste profile still shows requests made with song_id and artist_id set to non-null values. Is it possible that you're still posting the original file in your update?

↧

Check taste profile status

June 11, 2014, 7:48 am
$
0
0

Thanks for you reply. I am really appreciate your help.

Could you please show example of json file, which has success result, I will try to upload it, or make changes with mine?

Maybe the problem in some previous steps?

↧

Check taste profile status

June 11, 2014, 7:56 am
$
0
0

The JSON file I have just used as an update to a brand new taste profile is the first item in your most recent post.

↧
Search

Check taste profile status

June 11, 2014, 6:07 pm
$
0
0

Can you please explain that again? Are you saying the following JSON code we used worked for you in a new taste profile?

{"action":"update","item":{"item_id":"1_1","song_id":null,"song_name":"The Look of Love","artist_id":null,"artist_name":"Dusty Springfield","favorite":true}

↧
↧

tasteprofile/status glitch?

June 12, 2014, 5:53 am
$
0
0

I'm experience the same issue, what I can add is:

If I to a profile/status too early after doing an update, the profile/status will never be finished (somehow it aborts it)

↧

Check taste profile status

June 12, 2014, 9:23 am
$
0
0

Does anyone have any other ideas? We've tried everything. Could the problem be on echonests end? Could someone run the json taste update with their key to see if you get a result?

↧

Retrieving Detailed Pitch and Timbre Data from the Echonest API

June 12, 2014, 9:51 am
$
0
0

hunterkw,

Sorry, there's no way to extract pure pitch information (including octaves) from the analysis data. The pitch class provides enough data to understand the harmonic structures, but not to recreate the melody, for instance.

David

↧

Search playlists by number subscribed

June 12, 2014, 10:13 am
$
0
0

Haven't seen this exact question answered, but apologies if I've missed it.

I want to search for and identify playlists based on the number of people subscribed to it. I see that we can view number subscribed to one particular playlist. Is there a way to search all playlists by a range of number subscribed?

Thanks!

↧
↧

Check taste profile status

June 12, 2014, 12:42 pm
$
0
0

Hi,

It looks like in some of your taste profiles you have a number of successfully resolved items. I also took a look at one of your tickets (the one for the catalog containing 1001 items). I see about a third of the items that failed to resolve, however the remainder did successfully resolve, which you can see by reading the catalog and looking for the artist_id and song_id. Name resolution usually fails either due to bad data (bad misspellings, bad artist/song combinations) or because we do not have that artist/song.

Again, it does look like items are resolving in your taste profile so you should be able to work with that.

↧

Check taste profile status

June 13, 2014, 6:43 am
$
0
0

Looking at the ticket status "total_items" is how many items are in the ticket, "items_updated" is the how many items have been processed so far, "update_info" is a list of error messages (successfully resolved items do not appear). I checked the length of update_info and it was only 333.

(by the way, I am going to go scrub out your api key from your messages to prevent anyone from stealing it)

↧
Search

Check taste profile status

June 13, 2014, 6:47 am
$
0
0

Ohh ok, so how can I see the ones that were successful? I just need to import the echonest ID's into my db so I can get catalog match my songs to Rdios.. Sorry for being a pain, am I missing something really simple here? Thanks a lot for help.

Oh, and thanks for removing my API key, I didn't think about that.

↧

Check taste profile status

June 13, 2014, 6:55 am
$
0
0

If you have Rdio IDs for your songs (or IDs from any other streaming service that's part of Project Rosetta Stone), then there's a much simpler way:

Rather than putting artist and song names in your taste profile, and requiring us to try to string-match them to the Echo Nest world, just put the Rdio foreign IDs. To record a track play, for example, send us just a track_id of rdio-US:track:tXXXXXX instead of artist and song titles.

And similarly, you can use these Rdio foreign track (or artist) IDs anywhere else you're using the API rather than the Echo Nest IDs. So you shouldn't have to maintain any mapping on your end at all.

↧
↧

Check taste profile status

June 13, 2014, 7:00 am
$
0
0

If you want to read rdio ids out of your taste profile, just add bucket=id:rdio-&bucket=tracks to your tasteprofile/read call which will then include a "tracks" key on every resolved item which a list of objects with rdio foreign ids.

↧

Check taste profile status

June 13, 2014, 7:02 am
$
0
0

Elinton: Ok thanks a lot. I will try that now.

Eli@Echonest.com: Thanks for your answer. However I don't have Rdio ID's in my database. That's what Im trying to do. I was using this guide from the Rdio website http://www.rdio.com/developers/docs/guides/catalog-matching/

It shows how to catalog match my database with echonests, which in turn can grab the Rdio ID's? Is that correct?

It's all a little bit confusing for me, but my impression was that when I have linked all the songs in my db to a taste profile, I can query the Rdio ID's from Rosetta Stone.

↧

Check taste profile status

June 13, 2014, 7:06 am
$
0
0

I think it worked :) I get this return for one of my songs. Does this look right to you?

trueSOLQBYT1315CD47C27I Will SurviveARHIET31187FB42D8DGloria Gaynorrdio-US:release:a255272rdio-USrdio-US:track:t3128562TRDHHFW136E86C0EC9rdio-US:release:a4175568rdio-USrdio-US:track:t44615917TRQCGJF14476BB24C02014-06-11T14:16:252014-06-11T14:16:18CATUJXR1468B490549:song:1000_756SOLQBYT1315CD47C271000_756I Will SurviveGloria Gaynorrdio-USrdio-US:artist:r3637...

↧
Viewing all 1582 articles
Browse latest View live
Search