Closed bong0 closed 9 years ago
Hi,
Thanks for your feedback :)
Can you give me the soundcloud's track that soundcloud-syncer try to download please ? This will allow me to reproduce this error :). Thx!
@Sliim I'm sorry, the trackid is lost now. It went out of my shell buffer.
What I can tell you is that this was probably an API Issue. SC did not deliver the data the script expected for whatever reason. I think it's best to retry it a few times. Restarting the script helped for me.
The API also does other weird things like returning 401s when it shouldn't? (https://twitter.com/bong0/status/565103161325924353)
Hmm ok, I will look to implement a retry system when download fail, and go to the next track if max retry is reached.
For the 401 error, do you set a correct client-id
to the script ? (sc-syncer can determine itself the client id to use due to some change in the soundcloud website)
@Sliim yep that would also be my solution for that.
Yes the client ID is indeed valid. It's from an application I registered for that purpose and also works for all the other tracks. Auto determining the client_id
does not work anyway for me.
Yeah! Sorry, I meant "sc-syncer can't determine itself the client id to use due to some change in the soundcloud website" in my last comment.. :)
@Sliim Aah okay. It makes more sense for me anyway that everyone uses it's own client id. It's no point where I would expect a fix.
Hi!
soundcloud-syncer 0.3.1 should fix this issue ;). The default number of retry is 3, it can be customized with -R option. If the maximum retry is reached, sc-syncer go to the next track.
Traceback:
OS: Debian Wheezy armhf on Raspberry Pi 1 (armv6) installed via python3 pip