Open mrmaffen opened 8 years ago
Well, I guess this can be closed now as the API will be gone in 2 days
As of May 31st, The Echo Nest platform will no longer serve requests and developers will need to move over to the Spotify API.
Renaming this issue, its now about migrating off of echonest (anyone objects?)
Does this mean the Station functionality will no longer work? When I try to create a station I get "The Echo Nest returned an error: Network Error" in the interface and:
21:53:28 [0]: libechonest threw an error trying to parse the static playlist code 9 error desc: Network Error
In the console.
Yes, station functionality no longer works On Jun 9, 2016 6:55 AM, "facetoe" notifications@github.com wrote:
Does this mean the Station functionality will no longer work? When I try to create a station I get "The Echo Nest returned an error: Network Error" in the interface and:
21:53:28 [0]: libechonest threw an error trying to parse the static playlist code 9 error desc: Network Error
In the console.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/tomahawk-player/tomahawk/issues/460#issuecomment-224901692, or mute the thread https://github.com/notifications/unsubscribe/ABL17FD8gbPLvDFQEzxzQjmvoZ34HBdnks5qKBs2gaJpZM4HoGOe .
Ahh that's a real shame, it looked like an awesome feature. Do you think it will be possible to use the Spotify API for this functionality or will it be removed entirely?
I think the plan is to support a new type of plugins that generate infinite playlists. It is already supported in Android version and has reference implementation that uses Spotify api On Jun 9, 2016 08:15, "facetoe" notifications@github.com wrote:
Ahh that's a real shame, it looked like an awesome feature. Do you think it will be possible to use the Spotify API for this functionality or will it be removed entirely?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/tomahawk-player/tomahawk/issues/460#issuecomment-224927570, or mute the thread https://github.com/notifications/unsubscribe/ABL17OP4UzWUa0d4sIYMb0OouoxAor7Kks5qKC4BgaJpZM4HoGOe .
Any updates re: using Spotify API instead of EchoNest on desktop? I'm willing to help, if I can.
@yurrriq no updates. I think way forward would be to implement support for js 'playlistgenerator' plugins like tomahawk-android does, there is already a spotify-based implementation for that
Any chance of enabling the use of beets for this purpose?
Seems like we're hitting Echonest's rate limit of 360 requests/minute. Which doesn't sound like a lot tbh. Stations stop working because of this :S @jherskowitz Maybe we can ask them to increase the rate limit for our API key?