Webspace of Eric Brodeur

Perspectives on storytelling and digital cinema technology

Category: Avid

Conforming two sets of production sound

A situation we experienced on Hotel Noir was the use of two four-track field recorders to capture production sound. Ideally, one recorder should be used with enough tracks to handle the required microphone inputs.

As we processed dailies in the Avid, we selected a mixed-down audio track for our guide during the offline edit. A conventional audio turnover would consist of an EDL which is used to re-link all of the production sound tracks.

In our case we had two sets of production sound which cannot be represented in a single EDL. Also, there is no way to merge the A and B sets so we had to find another method of combining them.

What follows is a brief description of how we got both sets of audio turned over to the sound department.

Your sound team must be using an auto-conform tool such as Synchro Arts’ Titan. It ingests the EDL and builds a Pro Tools project using audio guide in the picture cut and the original production sound. If your sound team doesn’t implement this workflow you are looking at a mountain of time-consuming labor.

From the Avid, export an EDL of your sequence. In our case it referenced our A set of audio. The EDL contained a list of clips looking like this:

  • A0001
  • A0004
  • A0011
  • A0004
  • A0012
  • …and so on

When this is processed through Titan the four tracks of audio from set A are brought into Pro Tools.

Next, make a copy of your EDL and open it with a text editor. Replace the references to “A” with “B”. This assumes your location sound team used a consistent naming convention. In our case, set A contained tracks 1-4 and set B contained 5-8 and the filenames corresponded such as A0024 and B0024. Timecode matched as well.

Process this new EDL with Titan and the Pro Tools session will be populated with the second set of audio tracks. After some clean up work by the sound editor, the Pro Tools session will contain all of your production tracks.

Many thanks to Dan Snow at Anarchy Post for helping me find this solution.

Onlining RED with Avid Media Composer

If you’re shooting with RED and don’t need/want a traditional conform to the 4K RAW files, you can follow Oliver Peters’ excellent tutorial found here. He explains best practices for importing RED media for the offline edit and how to re-import and create a high-quality DNxHD 175X output.

I’m in the middle of doing this for Hotel Noir and wanted to mention a few things related to Oliver’s post.

As described in Step 8 we had to relink the sequence clips, not just the sequence. Change the bin display to show all clips/elements and relink from there. In some cases you may need to relink by repeating the Link to AMA command.

It’s best that you change the Source Settings for every clip to achieve the flat color space of the RAW footage. The quickest method is selecting all of the RECCODE clips then change Source Settings. Yes, you can select groups of clips and the settings will be applied to all of them.  It’s recommended to select the Default color settings then change RED color science (ie: REDcolor, REDlog) as needed.

Although you’ve changed the color settings for all clips used in the sequence, you must force Avid to update the clips in the timeline. Select your sequence then Clip > Refresh Sequence > Source Settings. You may be tempted to choose “All” but we experienced undesired changes to the clips by doing so.

Without a RED Rocket, our 3.2 GHz 8-core Mac Pro performed the conversion to 175X – for each reel – in about 5-7 hours. This equates to approximately 36 hours of render time for six reels and six hours per. This excludes any prep time.

You are your NLE

The release of Final Cut Pro X has brought to light a certain distinction amongst picture editors.

When Apple removed key features and changed the user interface, they received a wicked backlash. The biggest complaints weren’t with the UI but lack of OMF, XML, and EDL support. Without these it’s impossible to use FCPX in a professional environment such as network television and features films.

Despite this a number of editors I follow jumped into FCPX and praised it. But how are these professional editors using FCPX if it can’t turnover a show?

That’s when I realized my definition of “professional” isn’t the same as everyone else. We can debate this all day and not have a single answer. There probably should be a common understanding of the word “professional” as it relates to post-production but I think there’s another way to tell the difference.

You are your NLE.

The system you use is indicative of who you work for and the types of projects you engage. This is an observation, not a judgment.

Read an issue of POST magazine and it won’t take long to see that Avid Media Composer and Final Cut Pro (version 7) are used to edit network television and studio feature films. There is the occasional mention of Adobe Premiere but nothing else. No Vegas. No Edius. No iMovie. No Final Cut Pro X.

Perhaps those NLEs don’t have the necessary features required by Hollywood’s production workflow. Maybe those packages aren’t popular enough with employers and employees in the Hollywood system.

So, then, we’re back to the adage you are your NLE.

Can you name a studio feature edited with Vegas? When is the last time you heard a corporate training video editor going on about Avid?

Despite the disappointment of Final Cut Pro X to network television and feature editors, we may owe Apple a big thank-you for reminding us there are different industries with different needs.

Knowing your NLE is knowing your market.

This isn’t the most detailed or controlled test but on a whim I used InTech SpeedTools to benchmark two external drives attached to my MacBook Pro via FireWire 400: OWC/NewerTech Guardian Maximus (DIY kit) and the G-Tech G-RAID.

Guardian Maximus (DIY) with 1 TB storage:

  • RAID-1
  • Two 1 TB Western Digital drives
  • 7200 RPM
  • 32 MB cache each

G-RAID with 2 TB storage:

  • RAID-0
  • Two 1 TB drives
  • Speed and cache unknown

GMax results using Extended Test (20-100 MB): Read = 38 MB/sec, Write = 36 MB/sec

G-RAID results using Extended Test (20-100 MB): Read = 39 MB/sec, Write = 36 MB/sec

I’ll whip up some FireWire 800 tests at a later date.

AvidI recently solved a problem on my OS X 10.5.7 installation where the coreaudio driver was in a constant “not responding” state and slowing down Final Cut Pro.

Aside from rebooting, a permanent solution involved removal of the CoreAudio plug-in from the system (details here). Since I’m not using the Digidesign equipment which uses this particular CoreAudio plug-in, my work wasn’t impacted.

Should you need to completely reinstall the driver for any reason you can grab them for OS X 10.5 and OS X 10.4.

Powered by WordPress. Theme: Motion by 85ideas.