same problem with this API key : FILDTEOIK2HBORODV
given on the page :
https://developer.echonest.com/raw_tutorials/register.html
↧
curl (56) Recv failure: Connection was reset
↧
curl (56) Recv failure: Connection was reset
Started having a similar issue with the pyechonest package. Getting the following traceback: https://gist.github.com/ajw0100/9316661.
↧
↧
curl (56) Recv failure: Connection was reset
Same problem here!
↧
curl (56) Recv failure: Connection was reset
We are currently experiencing timeouts with track/upload calls. We are working to restore service.
↧
track/upload timeouts
We are currently experiencing timeouts with track/upload calls. We are working to restore service. Other APIs are not affected.
↧
↧
curl (56) Recv failure: Connection was reset
track/upload service is restored. Thank you for your patience.
David
↧
track/upload timeouts
Track/upload service has been restored. Thank you for your patience.
David
↧
My Music Recognition v1.0
My software hosted on this SourceForge page.
↧
curl (56) Recv failure: Connection was reset
↧
↧
Music identification for PC
thanks for sharing this information
↧
IP Block on DigitalOcean?
Calls to the identify API using curl are working fine on my local machine, but fail with a 403 denied error on my VPS - is there an IP block on DigitalOcean or something similar which might be causing this behaviour?
↧
IP Block on DigitalOcean?
what's the IP address that seems to be being blocked?
↧
IP Block on DigitalOcean?
192.81.223.118
↧
↧
State of API after Spotify Acquisition
Hey guys,
EchoNest is an important part of something I am building right now.
I was wondering whether I will be able to depend on your API endpoints, given that you have recently been acquired by Spotify.
Thanks, and congrats!
Dhruv
↧
State of API after Spotify Acquisition
Nvm, it looks like the API will stay open. Phew!
"The Echo Nest says that its API will remain free and open as part of the deal, which is good news for Spotify rivals including Rdio that use its services to power their own music recommendations."
↧
The Echo Nest has been acquired by Spotify - What does this mean for our API?
This week, we’ve announced that The Echo Nest has been acquired by Spotify, the award-winning digital music service. As part of Spotify, The Echo Nest will use our deep understanding of music to give Spotify listeners the best possible personalized music listening experience.
Spotify has long been committed to fostering a music app developer ecosystem. They have a number of APIs for creating apps on the web, on mobile devices, and within the Spotify application. They’ve been a sponsor and active participant in Music Hack Days for years now. Developers love Spotify, because it makes it easy to add music to an app without any licensing fuss. It has an incredibly huge music catalog that is available in countries around the world.
Spotify and The Echo Nest APIs already work well together. The Echo Nest already knows Spotify’s music catalog. All of our artist, song, and playlisting APIs can return Spotify IDs, making it easy to build a smart app that plays music from Spotify. Developers have been building Spotify / Echo Nest apps for years. If you go to a Music Hack Day, one of the most common phrases you’ll hear is, “This Spotify app uses The Echo Nest API”.
I am incredibly excited about becoming part of Spotify, especially because of what it means for The Echo Nest API. First, to be clear, The Echo Nest API isn’t going to go away. We are committed to continuing to support our open API. Second, although we haven’t sorted through all the details, you can imagine that there’s a whole lot of data that Spotify has that we can potentially use to enhance our API. Perhaps the first visible change you’ll see in The Echo Nest API as a result of our becoming part of Spotify is that we will be able to keep our view of the Spotify ID space in our Project Rosetta Stone ID mapping layer incredibly fresh. No more lag between when an item appears in Spotify and when its ID appears in The Echo Nest.
The Echo Nest and the Spotify APIs are complementary. Spotify’s API provides everything a developer needs to play music and facilitate interaction with the listener, while The Echo Nest provides deep data on the music itself — what it sounds like, what people are saying about it, similar music its fans should listen to, and too much more to mention here. These two APIs together provide everything you need to create just about any music app you can think of.
↧
State of API after Spotify Acquisition
Dhruv - the API is alive and well and isn't going anywhere. See the post in the announcements section that I just put up that gives more info on what is going to happen.
Paul
↧
↧
The Echo Nest has been acquired by Spotify - What does this mean for our API?
This is nice.
↧
Neophyte needing some basic guidance
Thanks for the help. I've been able to use the examples as guides and have successfully pulled some songs meeting my criteria. Any suggestions on how I can parse the response into a tool like Excel or Access so it is easier to work with?
↧
Neophyte needing some basic guidance
What do you mean by "easier to work with "? If you're thinking of writing some code to pull out bits of the responses from the API and manipulate them, I'd think it would be much easier to work with the JSON directly than to first load it into Excel or Access. Or are you trying to do this without programming still, and looking for a UI that helps you look through the data yourself? Even then, I'd think a tool for viewing JSON might be more useful than loading data into Excel or Access.
Or am I missing the point of what you're doing? Maybe say a little more about what specifically you're trying to do, and I might be able to offer better advice.
-Eli
↧