soundnode-app
soundnode-app copied to clipboard
Soundnode
tracks will not play
it was working fine this morning but when i got home when ever i try and play a track nothing happends and if i try and click into the track i get the oh no message.
Try removing the LocalStorage in the Soundnode setting and then rrstart Soundnode…
Problem appeared 30.06.2016. It is not possible to listen any track. Everything I got is silence. When I try to move forward a current track, I got the message: "Oh No. Something went wrong. I can't play this track :(". I tried to clean up local storage, run as admin. It didn't help. Version 0.6.4.
Same here :( Tried removing the LocalStorage, no help. Version 0.6.4.
Same problem i clean the LocalStorage and download the app again from the website. It's work now :)
Same here :( Tried removing the LocalStorage, no help. Version 0.6.4 on Ubuntu 14.04
EDIT solution for me -> remove localstorage and relaunch app
Exactly same problem here. Version 0.6.4, appeared yesterday.
Edit: Cleaning the local storage and restarting the app, helped. Thanks @clivend
It appears that we exceeded the Rate limit
stream:1 GET https://api.soundcloud.com/tracks/XX/stream?client_id=XX
429 (Too Many Requests)
@jakejarrett hey there, how did you find that log message? I haven't built from source (should probably do that) - but since it's a nodejs app - can I enable logging somehow? view a console even? would be good to know so I can make more meaningful bug reports!
also +1 on this issue. Clearing local cache and restarting app resolved for me.
@GrayedFox You can just press Control (Command on Mac) + / and it will open the devtools :smile:
@jakejarrett how could we avoid exceeding the rate limit? I was thinking of at least implementing session-based caching (so when you listen again to a song you won't make a new request) as allowed in the Terms of Use:
Your app may employ session-based caching, but only to the extent reasonably necessary for the operation of your app during that session, and any cached content must cease to be available, accessible or playable within your app at the end of that session.
We hit the Soundclou API limit that's the reason we can't play tracks.
I'm going to use the long weekend (starting tomorrow) to make some improvements on Soundnode and try to come up with a solution for this issue.
@weblancaster Jake Jarrett has already said that, what about my idea above to hit the rate limit less fast?
Cache doesn't sound good for me, especially that most queries comes from playing stream, so cache would let us save maybe few percents at most.
Eh? Cache would potentially save the end user a lot of data usage, and reduce how many times we hit the API. Not sure the best way to get the stats, but I could record all my traffic coming from Soundnode over several sessions using a proxy and gather data based on those requests most repeated. This would give us a base to decide what to cache first, based on traffic. Would be more useful with a larger user base (I.e. not just me) but hey, it's a start :)
I think caching will barely (if at all) help with this issue.
How about using a rotating pool of clientIds/tokens? If we just generate a few tokens and rotate between them wouldn't that mitigate the problem?
When soundcloud added limits, we talked about that but I don't remember what @weblancaster thought when I proposed using more api tokens and just randomly assigning them while user logs to app. That is still the best idea for me.
I'm just going to build something to let we know when Soundnode is close to hit the limit and swao to another developer id (I'm going to create two more developer ID)
@weblancaster that's not a scalable solution at all my friend. Also, possibly breaks terms of service?
Why don't we just ask the kids at Soundcloud what they think is the best solution? Maybe they have workarounds
You are correct not scalable but that's the only short term solution we have at the moment (I also have asked someone at Soundcloud.. there is nothing we can do)
Let me know if you have any idea (preferably following Soundcloud third party rules)
Clearing local storage and restarting Soundnode does not work for me.
Here are the contents of the JSON
{"errors":[{"meta":{"rate_limit":{"bucket":"by-client","max_nr_of_requests":65000,"time_window":"PT24H","name":"plays"},"remaining_requests":0,"reset_time":"2016/08/30 05:08:57 +0000"}}]}
Maybe there should be an option in the settings for the end-user to enter a developer id, if they wish.
I'm on Soundnode 0.6.4, since 0.6.5 is broken on Ubuntu 16.04 and I am in no mood to compile it from source (have better things to do with my time).
@onedrawingperday While not as friendly as a field in settings, you can open up Help > Developer Tools > Console, then run the following command:
window.localStorage.scClientId = "YOUR_PERSONAL_SOUNDCLOUD_CLIENT_ID"; // replace with your actual SoundCloud Client ID
It should persist across app relaunches so that you can keep rocking out even in the rare event that Soundnode's client id has been rate limited. See #858.
Hope that helps if this hasn't been resolved more directly by an app update before the next time the rate limit is exceeded.
resetting localstorage did'nt solve the issue for me, nor did re downloading, help would be apreciated :)
any updates? i run a really weak computer and the only way for me to listen to music and multi - task w/o google taking all my resources is with this :)