The right tool for the job.

In a previous post, I have noted that I have a strong prejudice for using Open Source/Free Software tools. However, when a proprietary tool is the only one that does the job, I will use it. I also believe that when I find a great tool, I should call it out.

PluralEyes is one of those great tools.

Anyone who is familiar with motion image post production, knows that one of the most odious task that an editor faces is syncing audio and video. For the purposes of quality, picture, and sound are often recorded on separate devices, necessitating their reintegration during the editing process.

Traditionally, this synchronization is done by identifying a common feature in both the recorded audio and video that can be matched up. Everyone is familiar with the archetypical movie slate.

Clapper

The idea is very simple. When you slate a scene, you are creating a simultaneous visual and auditory event that you can use later to synchronize sound and picture. There are also other methods based of a shared timecode in the camera and audio recorder, but these tend to be expensive and complicated.

The slate has one major draw back when shooting documentaries, and especially interviews. It is distracting as hell. If an interview spans a camera or audio recorder stop, you really don’t want to get up in the face of your subject with a slate in the middle of a conversation, just to get a good sync mark.

That’s where PluralEyes comes into play. So long as your camera footage has audio, PluralEyes will automagically synchronize your external audio with picture. All you have to do is drop the audio and video clips into the GUI in the correct order.

This is not a perfect fit with my tool chain. First of all, PluralEyes does not come in a native Linux version, so I have to run it in a Windows VM, (I haven’t tried WINE yet). Second, it does not support a edit decision list format that is compatible with the editing software I am using. It does output Final Cut Pro XML Interchange Format, which is well documented, and I should be able write a script to parse it into a form that Kdenlive can use, but in the mean time, I have a “good enough” workaround using PluralEyes’ media export function. What is undeniable is the  great gain in productivity compared to manual synchronization.

Finally I am making headway towards putting out some teasers,  and a Kickstarter video.

Thanks to Lars Fuchs for turning me on to this tool.

Tool Chain

Post-production Begins! I am only 1/2 through the interviews I plan to do; but with nearly 20 hours of interviews in the can, the time has come to get serious about post-production.

I have been syncing audio and picture, transcribing interviews, and bookmarking material for the trailer, promos, and Kickstarter video. (There, the cat is out of the bag!)

Anna Anthropy at Dorkbot CHI via D5100

 

 

 

 

 
I have a preliminary tool chain on place:

I am using Akimbo for bookmarking the interview audio. This allows me to listen to MP3s of each interview on an android device, bookmark them, and take brief notes. I can then reconcile this with the footage when I am at my editing station.

I am an open source kinda guy. As far as possible, I am working with free, (as in speech) tools. I am not fanatic about this however. If I need to purchase software to get a job done, I will; but I will always favor an open source solution for my needs.

Right now the suite of tools I am using consists of: Kdenlive for vidoe editing editing; Audacity and Ardour for audio mixing/cleanup; Gimp for image manipulation and color correction; Gimp and Inkscape for graphics; and many many other little utilites for various tasks.

The wonderful thing about working with Linux, is that so much of the work I need to do can be automated with scripts. I have writen scripts to wrap around ffmpeg to do transcoding and resolution shifting of the vidoe; extract MP3s for transcription; and even do background rendering. I use the Ubuntu Studio distrobution. The low-latency kernel makes working with audio and video painless. As I have gotten older, I apriciate the value of stability over having the most bleeding edge releases. As a result, in the last year or so, I stopped chasing the latest release, and settled on Ubuntu’s Long Term Support (LTS) (12.04 Precise Pangolin) as my OS of choice.

I may find in future that I need to accomidate the work flow of others, or that I just must have some feature only available in AfterEffects, of FinalCutPro. But for the time being. This tool chain suits me well.