Jump to content

Recommended Posts

Soundcloud Workflow:



  • Look up soundcloud songs
  • Open in browser
  • Download songs (hold CMD before pressing enter)
  • Set Downloads Path (type "Set Download Path for soundcloud" in Alfred and type a path like "/Users/Admin/Downloads/"


Download Link







The artist information is NOT included as the summary. I did this on purpose, it makes the workflow twice as slow because it requires two fetches from soundcloud's servers for every song, as opposed to one. If you would prefer to deal with the latency and see the artist information, I have included instructions for this under the readme. 



Thinking about adding an option to stream song via VLC or some other program. Any comments and/or suggestions are welcome!

Edited by Frostbite
Link to comment
  • 2 weeks later...
  • 4 weeks later...

I like this workflow but I see some possible improvements:


1 - why do you use the .py library when you can download soundcloud tracks with a regular cURL or a wget?

2 - if you require the .py lib, why don't you test whether the user has it and if not, not offer to download in subtitles

3 - getting the meta info doesn't require a second query to soundcloud with this kind of command (this searches for "macklemore"): 

curl "http://api.soundcloud.com/tracks?q=macklemore&client_id=YOUR_CLIENT_ID"

4 - you could put a boolean somewhere to offer people to download the covers and have a prettier display (you'll get the links in the metadata) (see this workflow:cl.ly/SqZM)

5 - when downloaded, you could write the metadata so that it looks prettier (cover optional) with this command line tool: eyeD3 (see same workflow as in 4).


Basically i like the workflow but it could be much better with some inspiration from the workflow mentioned in 4. :) 

Link to comment
  • 4 months later...

I just reinstalled this workflow and got the following error message:

Installing collected packages: soundcloud, fudge, requests, simplejson
  Running setup.py install for soundcloud
    /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'use_2to3'

  Running setup.py install for fudge

    warning: no files found matching '*.txt' under directory 'javascript/fudge'
    no previously-included directories found matching 'docs/_build'
  Running setup.py install for simplejson
    building 'simplejson._speedups' extension
    cc -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386 -g -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386 -pipe -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c simplejson/_speedups.c -o build/temp.macosx-10.9-intel-2.7/simplejson/_speedups.o
    clang: error: unknown argument: '-mno-fused-madd' [-Wunused-command-line-argument-hard-error-in-future]
    clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
    WARNING: The C extension could not be compiled, speedups are not enabled.
    Failure information, if any, is above.
    I'm retrying the build without the C extension now.

    WARNING: The C extension could not be compiled, speedups are not enabled.
    Plain-Python installation succeeded.
Successfully installed soundcloud fudge requests simplejson

The workflow is working fine.


Just posted this because I didn't remember having this error message when installing the workflow on one other Mac ( running OSX Mavericks too).

+ wanted to know if there something to worry about ?

Link to comment
  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...