Custom scripts help and documentation

Transducer provides a way for advanced users to run their own custom scripts after uploading a podcast episode. These scripts can be treated as though they are run from the Terminal directly, which means you can use your preferred scripting language.

Custom scripts are currently experimental. If you use custom scripts and have a suggestion for how they can be better, please email me. Also, if you have any trouble coming up with the right script to solve your problem, feel free to email me as well—I’d love to help you out.

Please note


Transducer executes scripts using the absolute path provided, and passes the following fields to the script as command line arguments in the order listed below.

  1. Podcast name
  2. Artist
  3. Episode title
  4. Episode description
  5. Episode duration (hh:mm:ss)
  6. Episode length (bytes)
  7. Path to local file (absolute)
  8. Hosted file URL. This value depends on the host you selected:

As an example, if I enter /Users/matthewpalmer/scripts/ as the script for an episode uploaded to Libsyn, Transducer executes the equivalent to the following Terminal command:

    $ /Users/matthewpalmer/scripts/ "My Podcast Name" "Matthew Palmer"\
      "#17: Episode title" "The episode description" "01:12:45" "43214632"\ 


Here’s an example of a Shell script I wrote to create a new Jekyll post for an episode of my podcast.

    # This script creates a new Jekyll post for a podcast episode uploaded to Libsyn.

    # Episode info from Transducer
    # Transducer passes each of these as command line arguments to your script

    # Where Jekyll stores its post files

    # Metadata for the post
    layout: episode
    title: \"$episodeTitle\"
    duration: \"$episodeDuration\"
    length: \"$episodeLength\"
    link: $fileURL
    subtitle: \"$episodeDescription\"

    YMD=`date '+%Y-%m-%d'`

    # Write metadata to the file for the post
    echo "$yaml" > ${postsDirectory}/$YMD.markdown