NPR is famous for beg-a-thons, wherein they lament the high cost of production and distribution and, oh yeah, solicit funds. It’s more pronounced now that they have started podcasting. More popular podcasts (particularly those who are making a go at doing it for a living) also have the same complaints.
I am slowly being converted to the opinion that the bandwidth complaint is a fundraising ploy. If they were really concerned about the cost of bandwidth they would attempt to minimize the use of bandwidth. But the bandwidth Jeremiahs are the same folks who apparently take no care to reduce their own footprint, putting out excessively, needlessly large audiofiles. YES it’s their podcast and their content and they can put it out however they wish, but if you want to beg for donations to cover your costs then I will expect you to attempt to minimize your costs.
Consider these ideas for reducing bandwidth; they take a bit of up-front scripting to make it work programatically, then it just motors along with zero added effort from the podcaster:
- Make a bittorrent feed available. Your listeners will happily donate bandwidth to keep your content flowing.
- Publish two podcast feeds: a feed with all the bells/whistles and a low-bandwidth feed.
- use a lower sampling rate. 44.1 is CD quality. Does your spoken word podcast require better-than-CD sampling? For our purposes, the Nyquist Rate predicts sampling should be 2x the highest audio frequency. Since the human ear hears roughly 20-20,000Hz, this explains the 44.1k sampling rate of CDs. If your podcast does not contain high frequencies at the extremes of human hearing then it does not need a high samping rate.
- use Variable Bit Rate (VBR) rather than Constant Bit Rate (CBR). This ensures no frame uses excessive bitrate to encode the audio.
- if you must use CBR, use a lower bitrate.
- if your podcast is mono, then encode as mono rather than stereo. Joint stereo reduced some of the waste when distributing mono in stereo encodes, but it’s still a waste.
- Consider voice presets in your favorite encoder. See the lame voice preset result below. This single change would probably make the biggest difference in podcasting bandwidth for most content producers.
- Consider other formats. If you insist on high bitrates, .ogg can shave a bit off the filesize (see below). If are really serious, use a speech-specific format like speex.
A specific example
Here’s the last file I downloaded from the feed of FreedomainRadio, your friendly neighborhood anarcho-capitalist (recommended, btw):
$ file FDR_2096_Sunday_Show_19_Feb_2012.mp3 FDR_2096_Sunday_Show_19_Feb_2012.mp3: Audio file with ID3 version 2.3.0, contains: MPEG ADTS, layer III, v1, 128 kbps, 48 kHz, Monaural
100576 Feb 21 01:14 fdrtest-lamevbr-noresample.mp3 97379 Feb 21 01:28 fdrtest.lamevbr-resample.mp3 53812 Feb 21 00:48 fdrtest-lame-voice-preset.mp3
68536 Feb 21 01:08 fdrtest.ogg
Changing nothing in the original 48kHz .wav, encoding with ogg vorbis gives us a 68.54MB file, for a 32.2% savings. Not bad, though one might lose some windoze/mac listeners. But as a second feed… Note that the .ogg advantage will decrease on lower quality sounds files. Speex is what you use for those.
50746 fdrtest.48k-original-sample.speex 14498 fdrtest.08k.speex 26394 fdrtest.16k.speex 33830 fdrtest.32k.speex