Auto-Podcasting for the Design Process
Okay, so I’m an inventor, for better or worse. Mostly worse. The clutter that is a necessary part of invention has to be seen to be believed. I’ve got chunks of hardware strewn about my studio, ready for soldering, repair, and reconfiguration. My hard drive is filled with various impenetrable chunks of code – modules, platforms, and other eratta. All waiting to be configured. So when two of these chunks end up working together in any way, let alone an incredibly sexy way to support creative development, it’s cause for celebration. And maybe some cleanup.
Last night at, oh, three a.m., I made one of these connections that had been staring me in the face – a way to easily share sonic research with creative teams that I work with a minimum of effort on my part. Last night, I set up my first automatically generated research podcast. I just upload files, and my website creates a podcast that the whole production team can sync with.
Here’s how it works. First and foremost, a little background:
1.) SET UP YOUR WEBSITE TO WORK FOR YOU.
A few years ago I configured my portfolio site to be a lot more easy to update. If you’ve ever played around with HTML and uploading files via FTP, you know that it’s a process that is fraught with time-consuming repetition and maintenance. When I started uploading 10-20 files for each of five shows I was working on at any given time, I knew I needed a more streamlined system.
At the time, I was learning more about PHP, a scripting language that enabled me to do handy things like set variable values, define helper functions, and repeat these helper functions. Best of all, I could grab open-source helper functions from friendly programmers and make them work for me.
For the portfolio site, I first set up a little loop that simply read the contents of a folder and displayed those contents as links. So now, instead of manually coding “a href=” tags for each linked file like a dutiful little hamster, I get an automatically generated page for each folder on my site, that looks like this page to the left here. I spent maybe 45 seconds of thought and time in creating this particular page – it’s simply the result of my site’s stylesheet rules and the file reader function of PHP. Pretty nice for under a minute plus upload time.
2.) SET UP YOUR WEBSITE TO WORK FOR YOUR USERS & CLIENTS
The big problem that eventually cropped up with this method was compatibility. Of course. With Internet Explorer. Of course. I made use of the quicktime “embed” player which is both really easy to set up from a coding stand point and the unfortunate victim in a lawsuit between Microsoft and ActiveX. Basically, Microsoft lost their ability to license the player in Internet Explorer, and for each embedded file, an IE user gets one of those really ugly “Enable ActiveX control on this page?” error messages that we all love so much. Gross.
So, I plugged in a new module: the configurable, flexible and totally free JW FLV Flash player. Combined with a MP3 Meta data reader, my research pages now look quite a bit sexier (and because it’s flash, it’s a lot more compatible). MP3′s have cover art, titles and artist authors embedded in them, and my website now reads that data and makes a lovely candy-coated interface.
Total thought put into this per show: Still 45 Seconds.
3.) IMPROVE YOUR WEBSITE’S PERFORMANCE AND EFFICIENCY
So that’s all nice and fine and flashy. Still a few compatibility issues, and suddenly the site is doing a lot of server-side processing, which causes some slowness in page loading. Some logic fixes improve all that, but is it ultimately useful? Last night, the final connection of how to really milk this system suddenly became clear to me.
The JW Player reads most of its information from an RSS feed – a feed that I am automatically generating using PHP and that MP3 Meta data reader.
Now, what else is an RSS feed that contains embedded audio files? That’s right: Podcasts.
So now, simply by providing the link to the RSS feed under the hood, my collaborators can SUBSCRIBE to my audio research. As I post stuff, boom, the entire team gets the new audio synced to their ipods with their This American Life episodes. And, at the same time, my process remains: Select Sound, Mix Sound, Upload Sound. No further configuration needed.
Go ahead: Try it on. You can subscribe to my serialized audio performance piece, Lexicon, in a few simple steps (If you haven’t heard this yet, by the way, it’s pretty representative of my sound design work. And I’m told it’s fun to listen to – though it was written five years ago, so some of the writing is still… let’s say formative. It’s all about the sound anyway):
1) In iTunes, Select Advanced: Subscribe to Podcast.
2) Enter the url: http://nikku.net/lexicon/podcast/rss.php
3) Let me know what you think.
Finally, if you’d like to try something like this setup for your own process, but don’t need all the bells and whistles (and want some simplicity!) there’s another excellent resource out there for you: The PHP script Podcast Generator creates an entire Podcast Content Management System and backend that can help you create a feed in a few steps. And of course blogging software often has some wonderful plugins that allow you post audio right in your blog’s RSS feed.
Multi-media research is good for multi-media work. More on that as season announcements draw nearer…
Buy Me a Coffee?
It’s no secret that early word of mouth is the key to a successful run. That’s why it’s a common business practice to fill the house with all your friends and industry folks that first cobwebby week of a run, so that the engine of buzz can get primed. Except there’s a pretty major caveat to papering – the practice often floods the tank, filling the books with reservations that never show up. It’s hard to shake the assumption that theater that you can see for free isn’t theater worth seeing, and so papered seats aren’t really taken as seriously as they should be. 
It’s hard to determine sometimes if technology is making our creative work better and more efficient or just more complicated in new and different ways. Part of the problem is that for most of this decade software and hardware engineers were moving in the direction of modular solutions.
It all gets demoralizing, though. I’m teaching some middle schoolers this week and we’re doing – of all things – a play called “30 reasons not to be in a play.” It’s unfortunately not all that ironic a title. Being in the play means rehearsal, and focus from the cast of 30 and tech crew of 8 while in a dark cafeteria watching other kids play outside in gorgeous weather. It means convincing often incredibly inflexible parents to cancel any number of poorly-scheduled piano lessons and dance lessons and baseball and soccer and errands. How can a seventh grader ask their parents to prioritize a school play when the parents don’t value the experience? It means remembering lines and overcoming awkwardness and shame to find… more awkwardness and shame and the very occasional moment of inspiration. It means being in the wrong place and not knowing what you’re doing… and doing that with absolute confidence. It means not texting your friends or checking your facebook account for nearly two hours most afternoons. 