-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maximum spotify api requets #5
Comments
ok I found the problem, it's to do with the fact that some spotify URLs are pointing to local songs.
A possible soultion could be to do the requets and the parsing in different rescue so that when parsing the json fails, we don't keep trying to request after 5 seconds. Another way could be to avoid url containing this "open.spotify.com/local" |
At one point this was working for mixed playlists that contained both standard and local songs, but the playlist format for that may have changed. I'll check it out when I get back to a computer. Thanks for the feedback! |
I have never run it on a playlist that large or hit an API limit, so I'm not sure how long they take to timeout. The cache will have saved all of the already processed tracks though, so resuming it should be fast :) |
Just looked at this again, and I can't reproduce it. It's a longshot given how much time has passed, but do you have an example of a recent playlist that still exhibits this behavior? |
Hi there, congrats for this tool. its really useful, specially when you want to try all the new streaming services out there.
do you know how many api requets is spotify supporting at the moment? I was able to run it half of my playlist, 4K songs. I was also wondering if the cache you implemented is to avoid requesting again for the already processed tracks? in this case, maybe I can try resuming it tomorrow? oh yeh...do you know after how long its a good time to try again?
cheers!
The text was updated successfully, but these errors were encountered: