3 ms·
At my company we have a bunch of content that's only archived on SoundCloud. The main barrier I've had to backing up original uploads (only available through th
by jeffbr13 11y ago
At my company we have a bunch of content that's only archived on SoundCloud. The main barrier I've had to backing up original uploads (only available through the web interface) is the terrible reliability of all the AJAX calls. Even with browser automation, it requires a LOT of error-handling just to navigate between resources successfully.
It seems that all these microservices[1] are there for the sake of blogging about using microservices[2] as there haven't been any new significant new features delivered in years, and the whole application now seems to be delivered through AJAX calls.
[1]: https://developers.soundcloud.com/blog/building-products-at-soundcloud-part-3-microservices-in-scala-and-finagle https://developers.soundcloud.com/blog/building-products-at-...
[2]: http://philcalcado.com/2015/09/08/how_we_ended_up_with_microservices.html http://philcalcado.com/2015/09/08/how_we_ended_up_with_micro...
- toomuchtodo 11y agoHave you tried using youtube-dl? It extracts the relevant data from Soundcloud's JSON API to perform the download: https://rg3.github.io/youtube-dl/ https://rg3.github.io/youtube-dl/ I know you mentioned originals are only accessible through the web interface, but I was not sure if you were aware of the JSON API.
- zimpenfish 11y agoOh, I didn't know that. I ended up writing my own SoundcloudSync.py to keep a backup. Not very sophisticated but easy enough to run by hand whenever I upload something new.
- zimpenfish 11y agoI seem to be getting originals through the JSON interface - the MD5s of the downloaded m4as match the MD5 of the m4as I've got in Audioshare.