All,
This issue has been resolved. track/profile should be working for all tracks and parameters again. Sorry for any inconvenience. Please report any new issues in the "Bugs & Problems" forum.
David
All,
This issue has been resolved. track/profile should be working for all tracks and parameters again. Sorry for any inconvenience. Please report any new issues in the "Bugs & Problems" forum.
David
I want to create dynamic playlist of spotify tracks. Currently I am using
Create dynamic playlist : http://developer.echonest.com/api/v4/playlist/dynamic/create?api_key=TAFYO7QHYKWQE791F&artist=akon
Call next song Api : http://developer.echonest.com/api/v4/playlist/dynamic/next?api_key=TAFYO7QHYKWQE791F&format=json&session_id=09d56ac060de45999c0dc09d8769d4e9
Get spotify trackId : http://developer.echonest.com/api/v4/song/profile?api_key=TAFYO7QHYKWQE791F&format=json&bucket=tracks&bucket=id:spotify-WW&id=SOMDLKR142C46A6648
But for few artists the tracks array returns nil value.
Please tell the correct way to do this.
Thanks.
amit - on your dynamic create call add two parameters to specify that you want the spotify ids returned in the results and that you want to limit the results to those only in the spotify catalog like so:
http://developer.echonest.com/api/v4/playlist/dynamic/create?api_key=YOUR_API_KEY&artist=akon&bucket=id:spotify-WW&limit=true
@Plamere - I also have question regarding similar topic -
In between thanks for your solution i was also facing same problem. :)
rahul.mane91 - dynamic playlists have no limit, you can call dynamic/next as many times as you want to get a song. Note that sometimes we may run out of songs depending on how constrained your playlist is. If you are creating static playlists, then the limit is 100 songs.
All of the playlist parameters are described in detail in the docs that are here:
http://developer.echonest.com/docs/v4/standard.html#static
Paul
Paul - Thank you so much.
Solved my problem and doubt.
Hello,
I'm using echonest's search service to get a ranked list of MusicBrainz recordings using the following URL:
http://developer.echonest.com/api/v4/song/search?api_key=
I have a few questions regarding that:
How do you know what's the hotness of a song? What's the criteria?
Which release do you show? Sometimes there are many releases in its release_group, how do you select one?
For example, for 294ecdcd-7dd3-4392-87fa-edeb1349bfd0 release_group you show the second release, but for 61180839-f4a7-407f-b86f-24c48eef4066 release_group the first release is shown in the API.
By the way, that would be nice to write somewhere in the doc that what you call "track" in echonest are actually "recordings" in MusicBrainz. It's pretty confusing because MusicBrainz also have "tracks", but those that you show are a different thing. I'm sorry if it's already documented and I didn't find it.
Thank you! Matt
mparodi - we currently only officially support musicbrainz artist ids. Any release or recording IDs that we return are not necessarily reliable or stable and the results you receive are likely to change without notice, so I would not rely on them to build anything. The officially supported rosetta IDs as shown on this page http://developer.echonest.com/docs/v4
We integrated echonest into our platform to perform the fetch function for the biographies, some of the bio's come up but some that exist via Wikipedia and other platforms aren't even coming up. Some of the names are pulling the biographies for other (unrelated) people this can ruin the credibility of my platform. How do we fix this?
This is the exact code we pass the artist name through
$echonest = new EchoNest_Client(); $echonest->authenticate($apiKey); $artistApi = $echonest->getArtistApi(); $results = $artistApi->search(array('name' => $arname));
majority of the musicians are Nigerians are their biographies are available.
Hi, We are using taste profiles and on each static playlist request we are getting almost same songs for each taste profile. These should be different right ?
here is my query http://developer.echonest.com/api/v4/playlist/static?api_key=_MY_API_KEY_&seed_catalog=CAJTVQW143767B23B3&type=catalog-radio&adventurousness=0.2&format=json&bucket=id:rdio-US&bucket=tracks&bucket=id:7digital-US&bucket=song_hotttnesss&bucket=audio_summary&results=100&max_duration=350&max_energy=0.8&min_energy=0.39999999999999997&min_loudness=-16&max_loudness=0&song_min_hotttnesss=0.38&song_max_hotttnesss=1.0&song_type=studio&distribution=focused&dmca=true&artist_id=AR2SHU51187FB5CDC0
Hi,
I'm new to EchoNest and I'm trying to write a small personal application to sort a music collection.
I have the name of each song and the artist and I want to retrieve the metadata in a format similar to this:
"metadata": {
"artist": "...",
"release": "...",
"title": "...",
"genre": "...",
"bitrate": ...,
"duration": ...,
}
Looking at the API documentation, it seems like EchoNest doesn't provide this unless I use the fingerprinting software. I was hoping I could query the API with an artist name and title and get the above info. Is that possible?
Thanks!
All of those fields are from an MP3 file's ID3 metadata tags, stored in the file. Our database could not return the bitrate of your own collection, as we don't have it. There are many pieces of software available that can return the ID3 tags of your collection. The ENMFP and Echoprint code generators use TagLib: http://taglib.github.io/
Theoretically, do "danceability", "energy", "loudness", "key", "mode", "acousticness", "liveness", and "tempo" values change when analyzing a track with and without vocals? I'd expect only "speechiness" to change in theory.
I get a request denied error from AWS when trying to access the analysis_url under Track API. (ex: https://echonest-analysis.s3.amazonaws.com/TR/A1B2C3D4E5F6G7/3/full.json). I have my API key setup, is there anything more I need to do?
There could be modest changes in those attributes. -- Paul
Hi Dhruv - the url you get back from the audio_summary expires after 10 minutes. If you re-request the audio_summary via the track/profile call you will get a fresh URL that you will be able to use to fetch the detailed analysis. -- Paul
I probably posted this in the wrong forum but i need someone to help me out with the Biography API, below is the exact code we use for fetching artist biographies on our platform:
$echonest = new EchoNest_Client(); $echonest->authenticate($apiKey); $artistApi = $echonest->getArtistApi(); $results = $artistApi->search(array('name' => $arname));
For example i have an artist called Wikzid, is Bio is available at Wiki but instead it fetches Wiki
or We search Vector it pulls up Vector, or when we search davido it returns some Russian guy.
majority of the musicians are Nigerians and their biographies are available. Maybe i can get a custom made API that fetches biographies for Nigerian musicians.
Will really appreciate any help i can get.
Cheers
Thanks for your reply, bwhitman. I understand that in the example those fields are taken from the ID3 tags. What I'm trying to do is to fetch such information (not bitrate, but genre, album, etc.) from echonest in order to fill in the ID3 tags.
Is this possible based on only knowing the artist and song title?
Thanks again for taking the time to reply!
No, we do not return per-song genre or album titles at the moment from any query.
The fingerprinting examples you are pointing to are the data stored in the local ID3 tag.