You can put this wherever it can be accessible on your path so you can run xld commands. Upon installation, it comes with a CLI folder with the xld binary. The \ escape characters are just in here to make this a little more readable for you, you don’t need them. t "Pretty Little Liars: The Perfectionists, S01E05" \
I’m going to use all of these, and point them toward the path of the file to target at the end of the command. Taffy can now be run with the taffy command, and can easily set fields like title, artist, track number, year, and genre. I set this up by installing Taglib, a prerequisite for Taffy, with Homebrew: brew install taglibĪnd installing Taffy with Gem. I found the command-line utility taffy, which works on top of taglib, as a simple way to automate this piece. I do this manually in kid3, which is a great little tool, but filling out title, artist, genre, etc. Technically, we can live without tagging, as Apple and other podcast platforms will pull that information from the RSS data, but I like to do it anyway in case the files end up on a hard drive somewhere and someone needs to know what they’re looking at. I’ll show you how I’m doing this-first with the terminal commands, and then by building it into a script. This file then needs to be tagged, converted to MP3, and sent up to the cloud. There are a number of steps involved in getting this thing from our microphones into your ears, so recently I’ve come up with a workflow that automates some of the set-up.Īfter finishing up recording and mixing, I export an audio file from Reader as, for example, plgm_episode_83.wav.
We record it ourselves and do some minor editing/mixing in Reaper, upload it for free on, and create the RSS feed that sends it to Apple Podcasts and Stitcher by posting on this very WordPress site. How I semi-automated our podcast workflow How I semi-automated our podcast workflowĭom Sinacola and I do our podcast, Pretty Little Grown Men, in a pretty DIY way.
0 kommentar(er)
