Seattle Documentary Filmmaker

Monthly Archives: August 2012

I had to deliver a revised video to a client this morning, which I thought was going to be as simple as navigating to the Replace Video File tab on Vimeo. A half-dozen upload attempts and 3.5 hours later, my 79meg video file finally finished uploading. Is it just me, or is Vimeo running painfully slow lately? But there was an upside to this delay: it forced me to take a close look at how I’m compressing footage for Vimeo. And I learned a few things about prepping files for Vimeo that are worth sharing.

Final Cut Pro X provides a super simple way to export to Vimeo – just hit Share > Vimeo. This works great if you just want to share a file once. But unfortunately, this doesn’t work for me at all, because I have to upload multiple revisions, and FCPX doesn’t support file replacement from within the app. Final Cut Pro X doesn’t have a way of exporting 1080 to 720 from the Share menu’s Export Movie dialog, so in the past I’ve always just exported 1080p and uploaded that to Vimeo, where it’s converted to 720 on their end.

But the slowdown forced me to create 720p files on my end before uploading, and I noticed that converting them using Quicktime 7 to 720p. left the files looking a little washed out and desaturated. I did some digging, and it turns out quite a few others have noticed this gamma shift as well. The good news is it’s fixable, but it requires some work.

The best tutorial on how to fix this is from Transposition Films blog post Best Compressor Settings for Vimeo V2. You don’t actually need Compressor to do this, however, just Quicktime 7. Here’s a simplified, non-Compressor based workflow that gets the job done.

2. Open the download and grab just this one file: x264Encoder.component. Copy it to your Macintosh HD/Library/Quicktime/ folder. Make sure it’s the top-level Library, not your User library.

3. Start (or restart if it was already running) Quicktime 7.

4. Select File > Export.

5. Name your file and at the bottom under Export choose “Movie to Quicktime Movie” and click “Options.”

6. Under Video, click “Settings.”

7. Under Encoder, choose X264.

8. Here’s how I set the rest (my clip was 23.987 footage – if you are using a different frame rate, set accordingly, but don’t set higher than 30 frames per second when encoding for Vimeo, even if shot at 60p). Note that I’ve set Restrict to 5,000K per Vimeo’s requested settings. I don’t think there’s any benefit to setting this higher, because Vimeo will recompress it on their end anyway.

9. Press “Options.” You’ll get a bewildering array of options, but don’t worry – you can accept the defaults on the first tab:

10. Accept defaults on second tab too:

11. On the Behaviors tab, set your native fps according to your footage frame rate. Be sure to check “use 3rd pass.”

The latest video in the series we’re making for Seattle Interactive Conference was officially unveiled today. It’s a peek at Seattle creative agency Digital Kitchen, the geniuses who make videos for the likes of BMW and Warner Brothers.

The best part of working on this project, besides meeting the friendly DK folks, was the opportunity to view so much jaw-dropping DK work. We were particularly inspired by the elegant simplicity of their Ask Away campaign, a series of documentary-style videos for the Atlantic Lottery. It’s commercial work worth sharing.

After my last post about audio syncing in FCPX, I thought I would give the new PluralEyes for FCPX a second look. When it first came out, I decided not to use it because it required creating project files to sync audio. I thought that meant you had to store files in projects, like in the bad old days on Final Cut Studio. But after further experimenting, I’ve discovered it’s possible to use PluralEyes to sync clips and keep them in the event library. But it involves some housekeeping. Here’s how it’s done.

1. Create an Event and import your video clips and the audio that you want to sync them with.

2. Create a temporary new project (I include the words “sound sync” so I can easily find it after and delete it) and place all of the video you want to sync into the timeline. Then, add all the audio files as connected clips. Creating this project is a temporary step – you will delete it as soon as the sync is complete.

3. Press Cmd-0 to view the project library. Select the project you just created, and from the File menu, choose “Export XML.” Save the file to your desktop.

4. Start PluralEyes. It’s a stand-alone application, not a plug-in, so you have to launch it separately. Once open, the interface presents like so:

5. Press “File” button and select the XML file you saved out in step 3.

6. Press “Change” button and review your options. I set mine as follows:

The options above are as follows:

Clips are in Chronological Order: This will speed up processing a bit if you place the audio and video clips into the timeline in order they were recorded.

Level Audio: I avoid this because I prefer to do my own audio leveling using FCPX’s Limiter plugin.

Use Markers: I haven’t yet found a reason to sync to markers, so I leave it unchecked.

Try Really Hard: Of course you want it to do that!

Replace Audio: By checking this, PluralEyes will create a new Event that contains all of the synced clips, with their native audio deleted, and the good audio connected. On DualEyes I never check this, but on PluralEyes, I do. If you need the reference audio, you can still get it as we’ll see in a moment.

Enabled Multiprocessing: Yes.

7. Click “Sync.” This runs the sync.

8. When the sync is finished, FCPX automatically opens and you will see that several things have been created:

a). A new project called “(your name) synced.” You should see the good audio moved into place below the reference tracks, like so. If you notice that some files are out of place or missing, double check your settings and run sync again (a common problem is checking “files are in order” when they aren’t.)

b). A new event containing a multi-cam clip called “(your project) mc.” I don’t see much use for this. The only reason I can think of is if you want to use reference audio. PluralEyes includes the reference audio in this clip, so that’s where you’ll find it if you need it.

c). A new event called “(your project) synced.” This is the one you want. It contains all of your synced files, minus the reference audio. This saves you having to go in and turn off the reference audio, a real timesaver over my DualEyes workflow if you are syncing lots of files at once.

9. If everything synced successfully, it’s time for cleanup. PluralEyes has created a whole bunch of stuff we don’t need, and we need to get rid of that stuff to keep our files organized. Start by deleting the project you created in step 2. You don’t want to have project files hanging around after sync is complete – you want all your files to live in the Event Library. Next, delete the project created by PluralEyes in step 8A. Finally, if you don’t need reference audio, delete the mutlti-cam event that it created. That should leave you with your original event, and the new event with the “sync” suffix. As a final cleanup step, let’s merge them.

10. Merge events. Click on the “sync” event and drag it over the original event.

Final Cut will merge the two events by creating a new Event, which by default is named same thing as the event you’re merging with:

Now all your files are where they belong, in the Event Library. You’ve successfully batch-synced all the audio. As a final step, I recommend highlighting the reference audio clips and pressing the delete key to mark them as rejected clips. This way, you won’t run the risk of using the crappy audio when you should be using the good stuff.

I’ve been cutting on Final Cut Pro X for more than a year now. And during that time, I’ve learned to hate working on rough cuts where the audio levels are too low, clipped, or noisy. It’s too tempting to yank on the volume levels of individual clips and introduce problems that will bite you down the line. So over the past year, I’ve evolved a workflow for prepping interview clips that is pretty close to perfect for us at Visual Contact. In our approach, we make the clips sound good as part of the import process, BEFORE we start cutting. It’s made our work a lot smoother, and ultimately it saves us time (and money). Here’s how we do it.

But first, some background on our production technique. When we shoot an interview, we record dual-system sound (reference audio on the camera, and two mics on the subject: a lav and a shotgun mic, recorded to left and right channels respectively, via a MixPre to Zoom H4N. All things being equal, we usually don’t end up using the lavalier audio, preferring the superior sound of a shotgun mic. But experience has made us believers in redundancy.

After a shoot, I import all of the files (audio and video) into Final Cut Pro X, which places all files into the Original Media folder of the Event. From there, my workflow involves the following steps, each of which I’ll explain below:

Batch-sync audio with DualEyes.

Organize files into Smart Collections.

Change sync audio files to Dual Mono.

Create synchronized clips.

Assign keywords to synchronized clips.

Fix glaring audio problems.

Step 1: Batch-Sync Audio.

While it’s possible to individually sync audio within Final Cut Pro X by selecting individual files and creating a sychronized clip, this only works when you know which audio file belongs with which video file. If you have a lot of both, you’re screwed. Unless you were slating everything, which we documentarians almost never do (in part because what I’m about to share with you is much faster).

Batch-syncing in our workflow is made possible with DualEyes. It creates audio files that are clearly labeled with both the video clip from which they are derived, AND the audio clip. This makes syncing them in Step 2 a snap. Note, the latest version of PluralEyes can also accomplish this – but the syncing process involves placing files into a timeline, exporting them out via xml, running PluralEyes, and then bringing them back into FCPX. If you use this method, be very sure to delete the project files that PluralEyes creates after the sync, so you don’t get confused about where your files are – they should only ever be in the Event Library.

So let’s get started. First, quit FCPX (so it doesn’t try read in the temp files that DualEyes is about to create). Open DualEyes, and create a new project. I save it to my Desktop, where I can remember to delete the temp files it creates after the sync. Now drag all your interview audio files and video files into the project.

If your shoot included clips unrelated to the interview such as b-roll, you CAN just drag everything in. It won’t hurt anything (unless you have a ton of clips). But it will take longer for DualEyes to run.

Before you click the scissors icon to begin the sync, check the options. Here’s my settings:

Correct Drift: This will create a new audio file that is timed to precisely match the reference audio. Check it.

Level Audio: This performs an adjustment to the audio levels, which is probably fine for quick and dirty projects, but if you want to have full control over how your dialog sounds, definitely leave this unchecked.

Try Really Hard: Of course you want your software to work hard for you, right? It takes longer, but it does a better job. Check it.

Infer Chronological Order: generally your files will be numbered sequentially, but if you are using multiple cameras or different audio recorders, leave this off.

Use Existing Extracted Audio Files: This saves time if you are doing a second pass on the files (for example, if it missed some files on first pass, and you’re trying again, it will use the same temp files without having to recreate them, saving time). Check it.

Replace Audio for MOV Files: Checking this box will strip out the reference audio from the MOV file and replace it with the good audio. I like to keep my options open, in case I want to use the reference, so I never check this.

Enable Multiprocessing: Check it.

Click the scissors to run the sync. Your machine will churn for awhile. When it’s done, take a look at the new files created in your Original Media folder:

Note that DualEyes has created audio files for you, which are perfectly timed to match the length of the MOV file. And, it titles each file with the name of the mov file AND name of the audio file, important for the next step. You’ll also see that a folder called DualEyes has been created. Delete it, after checking to ensure that a new audio file appears below each video file that you expected to synchronize. If any is missing, run the sync again.

Step 2: Organize Files into Smart Collections.

It’s time to start getting organized. Start FCPX, and open the event. I start by creating a Smart Collection for each of the media types in my project (for example, one called Stills for all the still photos, and one called Audio Only for the audio files.

I also create a temporary Smart Collection called Sync Audio to make the next step faster:

In this collection are listed all of the files that DualEyes created for you. They need some work, which we’ll do next.

Step 3: Change sync audio files to Dual Mono.

Choose the “sync audio” smart collection. Select them all in the event library (Cmd-shift-A). Then, open the Inspector. You should see something like this:

Notice that the default setting of Stereo. Change this to “Dual Mono.”

This will allow you to choose only the best-sounding mic (or to mix both mics) in later steps. But first, we need to create synchronized clips in FCPX.

Step 4: Create Synchronized Clips

Put the Event Library into list view (opt-cmd-2), and select the event title so that all clips in the event are displayed. At the bottom of the event browser, click the settings gear, and make sure you have selected these options:

This will ensure that all your clips are displayed by name, next to each other, like so:

Select the first movie file, hold down the command key, and select the audio file immediately under it (select the “drift corrected” version if you have more than one).

Repeat this for each file. When you’re done, your directory will be filled with synchronized clips, which are the ones you’ll be using for the rest of your edit.

At this point, I create a new Smart Collection called Sync Video, so I can keep track of all the new clips and have them all in once place for the next round of work, adding keywords.

Step 5: Organizing with Keywords.

In this example, my shoot included two interviews with different people. Later in the edit I’ll want to quickly find interviews with each person, so I’m going to assign keywords to each. To do this quickly using the files that have the good audio linked to them, I start by putting the Event Browser into Browse view (opt-cmd-1). Now I can see at a glance which clip has which person.

In the image above, you can see I’ve created a folder called “Interviews” into which I’ve created two keyword collections. To assign, I select all the clips with each person and drag them into their respective keyword.

If you’re lucky and your audio levels are perfect at this point, and you like the balance between the lav audio and the shotgun mic, you’re done. But because we live and work in the real world, it probably isn’t quite that neat. Your audio levels, like these, might be too low, and maybe there was an HVAC system running in the background that leaves a low level noise you want to remove. And in my case, the lav audio needs to be turned off altogether, because the shotgun sounds far better. The next step is where we do that, keeping basic adjustments where they belong – with the file in the event library, before editing starts.

Step 6: Fix audio problems.

In the Event Library, select the keyword collection with that contains the synchronized clips you want to work on. Select the first clip, and open it in the timeline.

You’ll see the clip above the attached audio below, in green.

Select the blue clip, and make sure you can see the Inspector (cmd-6).

Since this clip contains only our reference audio, turn it off entirely by unchecking the box under Channel Config.

Now go back into the timeline, and click on the green audio file. In the Inspector’s channel config, both tracks are enabled.

In my case, I want to turn off the lavalier track, which is on the right channel, because it is inferior quality to the shotgun mic.

Now that I’ve got the best audio quality, it’s time to check my levels. Here’s how the clip looks. I can see just by looking at the waveform that the volume is too low:

While playing our clip, the audio meters show the levels are bouncing between and -11 and -30 db. That’s too low. A good rough levels setting is between -6 and -20 db. Let’s fix that.

I could just yank up the volume, but that would leave us open to spikes of volume that might clip. I want to raise the levels without the danger of clipping, and leave any micro adjustments to levels to later editing. So I’ll use Final Cut’s Limiter effect, located in the Effects Browser, under Audio > Levels.

With the audio clip selected, double click the Limiter effect to apply it. It now appears in the Inspector.

Click the slider icon to bring up the HUD controls for the Limiter.

Here’s how I set mine:

Output Level: -3.5db. This means that the Limiter will “limit” the volume level to -3.5db, no matter how loud the clip gets. This is the correct setting if you don’t plan to use music under the piece. This is a pretty good baseline setting. If you know for sure that there will be music under the dialog, set it to -4.5.

Release: set to about 300ms for dialog.

Lookahead: leave it set to 2ms.

Gain: This will depend entirely on your clip. Drag the slider upwards until you are seeing levels that sound good, that range between -6 and -20 or so.

You will likely see some peaks reaching into the yellow in the timeline:

Listen to your clip one more time. In my case, I’m hearing an annoying HVAC system in the background that needs to be cleaned up. For that, I use iZotope RX, an insanely useful suite of audio repair plugins that work within FCPX. If you routinely work with dialog recorded on location, you won’t regret shelling out the $349 that it costs. It can also do miracles with clipped audio, which many audio engineers say is impossible to fix.

It’s beyond the scope of this tutorial to explain how to use iZotope, but in this case, I’ve applied the Denoiser effect, trained it to identify the noise with room tone I recorded at the location, then applied the setting to the clip to nix the HVAC. It doesn’t entirely remove the offending sound, but most of it is now gone.

At this point I’m done fixing things. It was a lot of work, and I don’t want to have to repeat it on every clip. So we’re going to select the audio clip, copy it (which also copies the effects which have been applied to it). Now, you’ll need to open each of the remaining clips, select the audio track, and choose Paste Effects.

You can select all of the clips at once, and paste the effects to all of them. But if you have individual channels turned on or off, as I have, you will have to open each clip individually to adjust that.

Now you’re all set to start cutting with the confidence that your clips will sound great from the moment they land in your timeline.

My most recent commercial piece, which Lisa Cooper and I made for Seattle startup Decide.com, is a great example of how a powerful Final Cut Pro X plugin called Neat Video can improve murky DSLR footage. We shot this piece on two Canon 60Ds, which like virtually all DSLRs, produce heavily compressed files that can get noisy when you lift the exposure levels.

Let’s start by taking a look at the finished video, and I’ll work backward from there.

Two challenges on this shoot combined to produce the noisy footage: mixed light at low levels, and monochromatic backgrounds. Let’s talk about mixed light first.

This office interior, like many, was lit by overhead fluorescent fixtures. But there was also big daylight windows. So the color temperatures didn’t match. My solution was to turn off the overheads, and set my white balance to daylight at 5400K, which I did with the employee interviews I’ll talk about shortly. The drawback to turning off overheads is that now the overall ambience of the room is darker. But, not so dark that I couldn’t bring them up to where I wanted them in post. But that’s where the problem comes in: lifting the levels in post introduces noise. And noise can look really ugly.

The second problem was the even tonality of the interview background, which was a bare, colored wall, which I hit with a Lowel ProLight to give it some life. But because of their highly compressed 8-bit codec, DSLR footage doesn’t hold up very well in large areas with the same color value. There just isn’t enough data available to make the subtle transitions appear totally smooth, especially when you have a gradient or subtle variations in color (a totally clear blue sky is another area where this problem often shows up).

In the example below, take a look at the grey background behind the subject. It’s essentially a gradation from darker shades of grey to middle shades of grey (actually, it was light green on left and grey on right before grading – grey throughout after).

As-shot section of video screen grab:

Notice there isn’t too much noise, but the image needs to be lightened quite a bit.

Graded, before Neat Video:

The color-adjusting and grading has improved the image dramatically, but also introduced lots of noise in the background. To help you see the noise, here’s a portion of the image cropped to 100 percent, at which the noise is most visible:

After Neat Video (below):

The noise is almost completely eliminated. Sweet. (Click the image above to view at 100 percent)

Here’s how it works.

First, download and install the Neat Video plugin for Final Cut. You can get a free trial, but it overlays a watermark, so to do any useful work, you’ll need to cough up $99. It’s totally worth it if you’re getting paid for your work.

Under the effects browser (Cmd-5), search for “noise.” The filter is called simply “Reduce Noise.”

Apply the filter to the selected clip in your timeline by double clicking the filter. It will appear in the Inspector, like so:

Click “Select to open” twice (for some reason it won’t open the first click). This will bring up these controls:

The first thing you want to do is click in the area where the most noise is, an area that has just noise, and no details that you care about preserving. In my case, the decision was easy: click and drag the box in the area against the background:

Under Filter Settings, you have the option to play with Luminance, Chrominance and Sharpening. I’ve found that it doesn’t seem to improve anything by fiddling with the first two defaults, so I recommend leaving them alone. Sharping is a powerful tool, so if you want to apply sharpening, be careful not to overdo it. It’s in effect the same thing as a sharpening effect, only it’s included within this plugin.

When everything looks good, click Apply in the lower right. Now, take a look at your Inspector, where you have a couple more options that you should leave alone until this point:

Temporal Radius
Temporal threshold
Adaptive filtration

Temporal radius refers to the number of frames that Neat Video analyzes when it’s determining how best to de-noise your clip. The higher the number, the more frames it looks at. Choosing a larger number than 1 will definitely improve your footage. BUT. It will SIGNIFICANTLY slow down your render times. And, at least on these clips, the footage looked plenty good enough at 2.

Temporal threshold should be lowered below 100 on footage that has a lot of motion, and raised above 100 if your footage is static. So, for my interviews, I chose 150 and it looked brilliant. Play with it until you see what looks best, or just accept the default.

Adaptive filtration should be checked only if the level of noise changes during your clip (ie if your camera was moving from a well-lit place to a dark place, for example). For an interview that is pretty static, leave it unchecked.

One final tip: Applying Neat Video to your clips should be the very last step in your editing process. Why? Because it slows your computer down big time. All of the complex calculations required to selectively remove the noise from your video will bring even a fast computer to a crawl. My iMac 2011 27″ i5 quad-core beast will let me work through just about anything, but not Neat Video. Plan to apply the clips and go for lunch. But when you come back, you’ll be thrilled with the results.