Transducer

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

When entering the “Script path” in Transducer, the path must be absolute (i.e. it must be something like /Users/matthewpalmer/scripts/... and not ./scripts/...).

Ensure that the script at the provided path is executable (run chmod +x /Users/matthewpalmer/scripts/script.sh to make a file executable).

Because the script will be run directly, it needs to start with a shebang (#!). For example, when running a Shell script the file should start with #!/bin/sh or for a Perl script #!/usr/bin/perl.

Arguments

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.