Open dblythy opened 7 years ago
@dblythy thanks a lot for this feedback.. this is definitely going to be helpful and I will take a look with more detail.
@weblancaster only thing is, as soundcloud use multiple resolve steps to get the stream_url, it takes longer to load than the native api. But still beats nothing.
I'm curious why is 15k? Don't you login the user? Why not use their rate limits? Sorry but I'm not familiar with the SoundCloud limits and didn't look the code here.
Damn, see that it is for each user! That's okey, probably, i'll try. :D But i believe it's not correct to say "15 000 tracks", cuz it may have more requests per track page.
What about allowing each user to enter his own Soundcloud API key? I know it doesn't sound like a good long-term idea, but for techy users or with a good tutorial, I guess it could do the trick for now
EDIT:
sorry, already in https://github.com/Soundnode/soundnode-app/issues/998
I am a developer and I have run into problems with soundcloud in the past. I came to soundnode to see how the API limits were dealt with here, however I realised the same issues occur.
I worked around the API limits by using the embed SoundCloud player. Here's what I did in my application:
I created an embed player with the URL requested to be played. Set the player to hidden, and used my own media controls to control the hidden embed player. So I used my own facing to control a hidden SoundCloud embed player.
You need the player https://w.soundcloud.com/player/?url= and the track permalink_url. Unfortunately I don't develop in the language soundnode is written in so I can't contribute to improving.