Get the Lowest Prices anywhere on Macs, iPads and Apple Watches: Apple Price Guides updated December 18th


How the AppleInsider podcast is recorded and edited

As the AppleInsider podcast approaches 75 episodes, one of the most common questions we receive is how the show itself is produced. Our host Victor Marks offers a rundown of his process, including the hardware and software used to bring the weekly news program to life.

The official AppleInsider podcast regularly ranks among the top 10 technology-related podcasts available on iTunes, and has been a weekly production for over a year now.

If you're a regular listener, you know that the sound quality of the podcast hasn't always been as listenable as it is today. With that in mind, let's talk about what we've settled on for making a decent quality podcast.


Microphone Quality is where the audio signal starts. If you haven't got a good microphone, you can't begin to capture good audio. We tried a number of microphones from a number of different manufacturers using a number of different ways to connect them.

Managing editor Neil Hughes has settled on using IK multimedia's iRig Mic ($99.99 on Senior editor Mikey Campbell prefers to use a MiC 96K by Apogee ($229 on Amazon). My own microphone is either an Electro-Voice Cobalt 7 ($59.99 on Amazon) or a Pyle PDM78 ($9.99 on Amazon), which is an affordable Shure SM57 clone. I use a MicPortPro as my XLR to USB interface.

The recording process

How we record is just as important as the microphones and equipment we use.

Early on, we recorded ourselves locally using QuickTime or audacity and then gave me links to the files to download and try and synchronize. If you remember, we had three or four participants in each episode at that time. Trying to synchronize the audio was madness.

Later, we used Skype and Ecamm's Skype recorder application. This allowed us to have my audio in one file and every other participant's audio combined together in one file. Synchronization was much easier, but the sound quality meant that my audio sounded better than everyone else's audio.

What we've arrived at today is a different approach. We use Skype to hold the call, to record the call, and either Zencastr's mixdown which uses's processing to adjust levels and minimize noise, or Auphonic's desktop applications to do it.

Zencastr has the benefit of recording everyone's audio locally in HTML5 cache, and then synchronizing and uploading it to the host's Dropbox account and local machine.


At this point we're almost done, but sometimes there are unnatural pauses or things we would rather leave unsaid on the podcast.

I'll import the audio into ferrite on iOS. Ferrite is an audio editor that allows me to detect the silence, fine-tune how aggressively I want to detect the silence and then using a "tighten" option, will shrink the audio across the whole podcast. The "tighten" feature is going to appear in a future app release, and will only be available if you purchase one of the in-app upgrades.

The last step to making the podcast ready for publication is to add chapter markers. Chapter markers work well in Marco Arment's Overcast app, and while we don't make chapter markers for every episode, it's something we've done for a few episodes by listener request.

The feedback you give us really does make a difference. We've tried using Audacity for chapter markers, and settled on Thomas Pritchard's Podcast Chapters for Mac as the best solution.


Zencastr is the project of Josh Nielsen, and it exists to solve both the audio quality of participants not local to the host, and solve the synchronization problem.

It's not always perfect, in that audio clocks are independent to the computer and not in perfect sync. If you record for long periods of times, the clocks can drift and audio can get out of sync. Zencastr handles this pretty well. They both record the audio of Skype or other voip apps, and also record over it's own VOIP service. Only one participant needs to have a login account for Zencastr, making it easy to use with guests. You login, create an episode, give the link to the guest or other participants, and as soon as everyone's got their mic inputs sorted out (built-in versus external mic), start recording.

One benefit of Zencastr is that even if the VoIP connection is shaky, as long as the connection holds up at all, the local recordings will be good.

There have been times where I've been traveling, and I haven't been able to actually hear the other people on the call and have had to guess at what they've said, but because they kept talking, the local recording cache that Zencastr uses has saved the show. When you stop recording, it uploads everyone's audio to your dropbox, and then allows you to kick off post-production. The post-production used is powered by Auphonic.


Auphonic, made by Georg Holzmann, is many things. It's a website: There, you can buy credits for minutes of audio to be processed. You can process a single audio file, or you can upload multiple files of the exact same length (thanks, Zencastr!) and process them into a single file - it will adjust the levels of each, and remove noise from them, making the gain reasonable for our listeners who like to hear us while running, for example.

But Auphonic is also a pair of desktop apps. I've used Auphonic Multitrack when I wasn't aware that Zencastr used it behind the scenes, and before we used Zencastr. The desktop app doesn't have all the features of the web app, but it works offline, and once purchased, it doesn't require the reloading of credits for processing.

The Auphonic web app can take a text file of chapter markers generated by an audio editor like Audacity to make podcast chapters. The AppleInsider podcast used this feature once, but Audacity is the linux of audio editors, and isn't always the easiest thing to work with. It's good, but it's got some rough spots. Kudos to Auphonic for being compatible.

All tracks have to start and stop at the same time. Use one person per audio track, and put music in separate tracks. It processes the tracks individually as well as combined, to result in the fastest way to get to a good mix. The desktop app is barebones - you drag tracks in, you choose the target loudness, and select whether or not to use the adaptive leveler and crossgate options, and process the audio. There's very little to go wrong.

Being able to process audio when I'm mid-flight is also a great benefit.

Georg is prolific, and Auphonic doesn't stop there. It's also an app for iOS, and acts as a recorder. This app is great, but it doesn't work as well for our podcast needs because we have difficulty getting VoIP audio to use a microphone external to the iOS device. Some of this is because we were using lightning connections, and some of it is because even after getting a headphone jack compatible audio interface, we ran out of patience for trying additional microphones.

The biggest credit of getting our levels right, and right from speaker to speaker, keeping the noise minimal, and cross-gating so we don't speak over each other as much, goes to Auphonic.


Ferrite is a new addition to my toolbox. I used it in January to record the interview with iMovie team lead and Marathon Laundry founder, Glenn Reid. It does an excellent job of being both a recorder and audio editor.

As an audio recorder, if I use a microphone source like a pair of the IK Multimedia iRig Lavaliers daisy-chained, I can record one participant in the left channel and the other in the right- which makes it easy to take both tracks to Auphonic if I haven't got levels adjusted well from the start.

One of the features I use the most, even when I'm not using it as a recorder, is for quickly detecting and removing silence. I import the audio from the laptop using the old iTunes method.

You click on your iOS device in iTunes, scroll down past the installed apps to the ones that have storage you can save from or upload to. I select Ferrite on the left and drag the audio into the right pane, and then on the iOS device import the audio from iTunes. Tap and hold on the audio in Ferrite to select it all, tap on Strip silence, and adjust the controls at the bottom of the screen until you see the silence you want to get rid of highlighted.

The problem is, you now have all this silence between audio clips you want to keep.How do you compress them to pack the audio in tighter?

Purchasing either one of the two available in-app upgrades will enable the "tighten" feature. This feature was made available to us through TestFlight betas of the app and should be available soon. In the app's settings, I turned on two-finger-swipe to select the audio, and swiped across the whole audio, then tapped on "tighten" to collapse it all. There's an easier way, like using a keyboard and pressing Command-A, but this is how I get it done on the fly.

Podcast Chapters

We had a few requests for chapters in Overcast. You people who listen are the best, most handsome, and in possession of a taste for the finer things in life that I could ever hope to meet.

I was happy to attempt to put chapters on the podcast, and Thomas Pritchard of Podcast Chapters helped. Pritchard makes the one of the finest applications for reviewing at high speed and adding chapter markers suitable for use with Overcast.

The process is really simple. Import the MP3, being playing it, and Command-N to add a chapter at the appropriate point. Give the chapter a title, optionally a URL, and that's it. Export it, and upload the resulting file to the Web server. It's simple, without a lot of features, but it doesn't need that many - it just does the one thing well. I do like that it allows for playback at higher speeds, so I can listen through it to find the places in the audio that should be chapters that much faster.


This is how we podcast. It's perhaps not the most streamlined of things, but all of the apps are affordable in the scheme of things, and are easy to use.

The overriding thing to take away from this is that it's possible to get decent audio on a budget with a combination of easy to use applications.

It took us a while to arrive at this workflow, and we considered more expensive products you recommended to us, but this seems to be the best route we could put together on an intentionally very low budget.

The real takeaway here is: support the independent developer. Every one of these applications was made by just a handful of people, frequently consisting of one-person teams. The value for money is hard to argue with, and the results are ones you can hear for yourself.